REST pagination shape
UnscoredObserved
What we found
The GET /workspaces operation declares a typed cursor/token parameter and a continuation field in its response schema.
Why this is unscored
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
When this matters
Detected interface; pagination only for collections, async only for long-running jobs, batch only for multi-item operations
Usable schemas and operation patterns can reduce ambiguity for clients. More endpoints or constraints alone do not establish that an operation is easier to use.
Evidence basis
These sources inform the check. They do not validate our exact point weights.
Guidance recorded with this scan · 2026-10-15. Recorded scores are unchanged.
Recorded evidence
REST async-job pattern
UnscoredNot observed
What we found
No valid OpenAPI/Swagger artifact with operations was found.
Why this is unscored
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
When this matters
Detected interface; pagination only for collections, async only for long-running jobs, batch only for multi-item operations
Usable schemas and operation patterns can reduce ambiguity for clients. More endpoints or constraints alone do not establish that an operation is easier to use.
Evidence basis
These sources inform the check. They do not validate our exact point weights.
Guidance recorded with this scan · 2026-10-15. Recorded scores are unchanged.
Recorded evidence
No public evidence URL recorded for this check
Parameter constraint coverage
UnscoredObserved
What we found
125 parameter/request-body leaves across 25 operation(s): 75 machine-checkable (60%), 13 declare an enum (10%), 93 carry a description (74%), 21 have neither a constraint nor a description (17%).
Why this is unscored
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
When this matters
Detected interface; pagination only for collections, async only for long-running jobs, batch only for multi-item operations
Usable schemas and operation patterns can reduce ambiguity for clients. More endpoints or constraints alone do not establish that an operation is easier to use.
Evidence basis
These sources inform the check. They do not validate our exact point weights.
Guidance recorded with this scan · 2026-10-15. Recorded scores are unchanged.
Recorded evidence
OpenAPI specification
5/5 ptsCross-verified
What we found
Valid OpenAPI 3.1.0 spec at https://api.replit.com/openapi.json: 25 operations, 75 schemas, 100% response coverage, servers declared.
How this affects the score
These are recorded points before the total is normalized to 100.
When this matters
Interface-enabled product; no requirement to implement every protocol
REST, GraphQL, MCP, SDKs and CLIs offer alternative or complementary access paths. The useful choice depends on the task and client; no single format serves every workflow.
Evidence basis
These sources inform the check. They do not validate our exact point weights.
Guidance recorded with this scan · 2026-10-15. Recorded scores are unchanged.
Recorded evidence
CLI availability
UnscoredObserved
What we found
A command-line tool is mentioned at https://docs.replit.com/features/sdks/object-storage-javascript-sdk, with no install command, package reference, or formula link on the page (0 install commands, 0 package references, 0 command-documentation markers).
Why this is unscored
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
When this matters
Interface-enabled product; no requirement to implement every protocol
REST, GraphQL, MCP, SDKs and CLIs offer alternative or complementary access paths. The useful choice depends on the task and client; no single format serves every workflow.
Evidence basis
These sources inform the check. They do not validate our exact point weights.
Guidance recorded with this scan · 2026-10-15. Recorded scores are unchanged.
Recorded evidence
A2A Agent Card
1/3 ptsParseable
What we found
An A2A Agent Card is described at https://docs.replit.com/.well-known/agent-card.json, but it is missing required fields (name, description, version, supportedInterfaces, or skills).
How this affects the score
These are recorded points before the total is normalized to 100.
When this matters
Only a positively identified matching protocol
Versioned interface declarations are observable signals. Broad adoption and cross-client utility are not established by declaration presence.
Evidence basis
These sources inform the check. They do not validate our exact point weights.
Guidance recorded with this scan · 2026-10-15. Recorded scores are unchanged.
Recorded evidence
GraphQL schema completeness
UnscoredNot observed
What we found
No GraphQL endpoint was observed in a scanner-fetched declaration or GraphQL-shaped response. GraphQL depth probe: No GraphQL endpoint was observed in a scanner-fetched declaration or GraphQL-shaped response.
Why this is unscored
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
When this matters
GraphQL and relevant operation shape; introspection optional
Additional contract evidence may substantiate an existing capability. Disabled production introspection must not create a penalty.
Evidence basis
These sources inform the check. They do not validate our exact point weights.
Guidance recorded with this scan · 2026-10-15. Recorded scores are unchanged.
Recorded evidence
No public evidence URL recorded for this check
GraphQL pagination
UnscoredNot observed
What we found
No GraphQL endpoint was observed in a scanner-fetched declaration or GraphQL-shaped response. GraphQL depth probe: No GraphQL endpoint was observed in a scanner-fetched declaration or GraphQL-shaped response.
Why this is unscored
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
When this matters
GraphQL and relevant operation shape; introspection optional
Additional contract evidence may substantiate an existing capability. Disabled production introspection must not create a penalty.
Evidence basis
These sources inform the check. They do not validate our exact point weights.
Guidance recorded with this scan · 2026-10-15. Recorded scores are unchanged.
Recorded evidence
No public evidence URL recorded for this check
GraphQL batch mutations
UnscoredNot observed
What we found
No GraphQL endpoint was observed in a scanner-fetched declaration or GraphQL-shaped response. GraphQL depth probe: No GraphQL endpoint was observed in a scanner-fetched declaration or GraphQL-shaped response.
Why this is unscored
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
When this matters
GraphQL and relevant operation shape; introspection optional
Additional contract evidence may substantiate an existing capability. Disabled production introspection must not create a penalty.
Evidence basis
These sources inform the check. They do not validate our exact point weights.
Guidance recorded with this scan · 2026-10-15. Recorded scores are unchanged.
Recorded evidence
No public evidence URL recorded for this check
GraphQL async job patterns
UnscoredNot observed
What we found
No GraphQL endpoint was observed in a scanner-fetched declaration or GraphQL-shaped response. GraphQL depth probe: No GraphQL endpoint was observed in a scanner-fetched declaration or GraphQL-shaped response.
Why this is unscored
Additional evidence for this capability. It earns no separate points, so observing another related signal does not count twice.
When this matters
GraphQL and relevant operation shape; introspection optional
Additional contract evidence may substantiate an existing capability. Disabled production introspection must not create a penalty.
Evidence basis
These sources inform the check. They do not validate our exact point weights.
Guidance recorded with this scan · 2026-10-15. Recorded scores are unchanged.
Recorded evidence
No public evidence URL recorded for this check
MCP resource listing
UnscoredCould not verify
What we found
Could not read live MCP resource listing from any declared endpoint (0 connected, 1 required authentication, 0 not probed before the scan deadline, 1 unreachable or invalid). Live MCP probe: 7687 ms, 3 protocol request(s).
Why this is unscored
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
When this matters
Detected MCP server and advertised tool/resource capability
Live listings and contracts help agents discover tools and understand their inputs. These related observations remain unscored pending calibration of their contribution to successful tool use.
Evidence basis
These sources inform the check. They do not validate our exact point weights.
Guidance recorded with this scan · 2026-10-15. Recorded scores are unchanged.
Recorded evidence
Per-server results
- https://mcp.replit.com/server/mcp: Authentication was required before live resource listing could be read. (Could not verify)
- https://replit.com/integrations: Live resource listing could not be read because the endpoint was unreachable or invalid. (Could not verify)
MCP resource quality
UnscoredCould not verify
What we found
Could not read live MCP resource quality from any declared endpoint (0 connected, 1 required authentication, 0 not probed before the scan deadline, 1 unreachable or invalid). Live MCP probe: 7687 ms, 3 protocol request(s).
Why this is unscored
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
When this matters
Detected MCP server and advertised tool/resource capability
Live listings and contracts help agents discover tools and understand their inputs. These related observations remain unscored pending calibration of their contribution to successful tool use.
Evidence basis
These sources inform the check. They do not validate our exact point weights.
Guidance recorded with this scan · 2026-10-15. Recorded scores are unchanged.
Recorded evidence
Per-server results
- https://mcp.replit.com/server/mcp: Authentication was required before live resource quality could be read. (Could not verify)
- https://replit.com/integrations: Live resource quality could not be read because the endpoint was unreachable or invalid. (Could not verify)
MCP multi-surface coverage
UnscoredCould not verify
What we found
2 MCP surfaces were declared; 0 completed live sessions. Live MCP probe: 7687 ms, 3 protocol request(s).
Why this is unscored
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
When this matters
Detected MCP server and advertised tool/resource capability
Live listings and contracts help agents discover tools and understand their inputs. These related observations remain unscored pending calibration of their contribution to successful tool use.
Evidence basis
These sources inform the check. They do not validate our exact point weights.
Guidance recorded with this scan · 2026-10-15. Recorded scores are unchanged.
Recorded evidence
Per-server results
- https://mcp.replit.com/server/mcp: This declared MCP surface requires authentication; no authorization was attempted. (Could not verify)
- https://replit.com/integrations: This declared MCP surface was unreachable or did not complete a valid protocol session. (Could not verify)
MCP transport version
UnscoredCould not verify
What we found
Could not read live MCP transport modernity from any declared endpoint (0 connected, 1 required authentication, 0 not probed before the scan deadline, 1 unreachable or invalid). Live MCP probe: 7687 ms, 3 protocol request(s).
Why this is unscored
Measured, but not yet weighted. It adds no points and its absence subtracts none. Scoring requires calibration of reliability, applicability and overlap with existing checks.
When this matters
Detected MCP transport and negotiated version
A compatible negotiated protocol version helps clients and servers communicate. An older supported transport can still be usable.
Evidence basis
These sources inform the check. They do not validate our exact point weights.
Guidance recorded with this scan · 2026-10-15. Recorded scores are unchanged.
Recorded evidence
Per-server results
- https://mcp.replit.com/server/mcp: Authentication was required before live transport modernity could be read. (Could not verify)
- https://replit.com/integrations: Live transport modernity could not be read because the endpoint was unreachable or invalid. (Could not verify)
A2UI over MCP
UnscoredCould not verify
What we found
No adoption signal was detected, but endpoint discovery was incomplete or at least one declared MCP endpoint lacked readable list metadata, so site-level absence is unmeasurable. This metadata-only check did not call tools or read app resources.
Why this is unscored
An emerging convention, not a universal requirement. It adds no points and its absence subtracts none. Adoption and reliable testing must justify any future weight.
When this matters
Detected application UI surface
An embedded interface can support interactive workflows. Many tools work without a user interface, so its absence is not a general readiness failure.
Evidence basis
These sources inform the check. They do not validate our exact point weights.
Guidance recorded with this scan · 2026-10-15. Recorded scores are unchanged.
Recorded evidence
Per-server results
- https://mcp.replit.com/server/mcp: Authentication was required before MCP Apps list metadata could be read. (Could not verify)
- https://replit.com/integrations: MCP Apps list metadata was unreachable, invalid, or inconclusive. (Could not verify)
MCP Apps UI metadata quality
UnscoredCould not verify
What we found
No adoption signal was detected, but endpoint discovery was incomplete or at least one declared MCP endpoint lacked readable list metadata, so site-level absence is unmeasurable. This metadata-only check did not call tools or read app resources.
Why this is unscored
An emerging convention, not a universal requirement. It adds no points and its absence subtracts none. Adoption and reliable testing must justify any future weight.
When this matters
Detected application UI surface
An embedded interface can support interactive workflows. Many tools work without a user interface, so its absence is not a general readiness failure.
Evidence basis
These sources inform the check. They do not validate our exact point weights.
Guidance recorded with this scan · 2026-10-15. Recorded scores are unchanged.
Recorded evidence
Per-server results
- https://mcp.replit.com/server/mcp: Authentication was required before MCP Apps list metadata could be read. (Could not verify)
- https://replit.com/integrations: MCP Apps list metadata was unreachable, invalid, or inconclusive. (Could not verify)