Atlas entry

textforagents.com

5 capabilities over MCP. The inventory is incomplete. First atlas observation.

Observed · passive: no tools called, no credentials sent · sha256:07f2e0…e9c1

Surfaces

5 protocols checked

ARDNot foundNo document retrieved
A2Ainvalid0 skills
MCPValid2024-11-05 · 5 tools · resources not advertised · prompts not advertised
OpenAPINot detected0 operations
WebMCPNot detected0 declarative form tools · experimental
Exact states and meaning
  • ARD
    absent

    Exact state: not found · No document retrieved

    The supported discovery location returned no matching document.

    Not found does not prove the service exposes no such interface elsewhere.

    Not observed / not fetched

  • A2A
    failed

    Exact state: invalid · 0 skills

    InterfaceDelta retained the machine state “invalid” without assigning an additional meaning.

    Not observed / not fetched

  • MCP
    observed

    Exact state: valid · Revision 2024-11-05 · 5 tools · resources not advertised · prompts not advertised

    A usable protocol document was retrieved and validated.

    Directly observed

  • OpenAPI
    absent

    Exact state: not detected · 0 operations

    No endpoint was established from the evidence and scope that InterfaceDelta inspected.

    Not detected does not prove that no endpoint exists.

    Not observed / not fetched

  • WebMCP
    absent

    Exact state: not detected · 0 declarative form tools · experimental

    No named declarative WebMCP form tools were observed in the origin root HTML.

    Script-registered tools and other pages are not observed, so this does not mean the site has no WebMCP tools.

    Not observed / not fetched

Capabilities

5 · inventory incomplete

The atlas shows each capability by its plain identifier, inputs and declared sign-in. Publisher descriptions, paths, links and source evidence are not published here.

A2A skills 0+ observed

Inventory incomplete. The displayed count is a lower bound; missing items do not prove removal.

None recorded in this Passport.

MCP tools 5

  • claim_trial

    inputs apply_shims, check, clients, full_matrix and 6 more

  • conformance_check

    inputs apply_shims, clients, full_matrix, idp_shape and 1 more

  • run_history
  • subscribe_solo

    inputs apply_shims, check, clients, full_matrix and 5 more

  • subscription_status

Not observed in this Passport: MCP resources, MCP prompts, OpenAPI operations.

Declared and observed

5 tools declare hints; the AI readings agree with all 0 that have a reading.

A disagreement is not a finding about the service: either side can be wrong. How we compare declarations and readings.

Atlas history

1 observation

  • 5 capabilities · MCP 2024-11-05 · MCP endpoint validFirst observation
    Fingerprint and versions
    Fingerprint
    07f2e003dbbe9c402aea47125e6b6d9101348e2f0f9bdb5bc9f9ea7381dde9c1
    Passport schema
    0.5.0, passport-semantic-v4
    Consistency
    MCP_PROMPTS_ADVERTISEMENT_LIST: not applicable · MCP_RESOURCES_ADVERTISEMENT_LIST: not applicable · MCP_TOOLS_ADVERTISEMENT_LIST: match · OPENAPI_MCP_EXPLICIT_MAPPING: not applicable

Each class compares an observation with the previous atlas observation. Runs of unchanged observations are grouped. Struck values are what the previous observation recorded; inserted values are what this one recorded.

About this entry

  • com.textforagents/mcp-oauth-client-interop-conformance
    Listed

    Official MCP Registry · first listed 3 Nov 2026 · last listed 3 Nov 2026

Passive observations of a public interface listed in the Official MCP Registry. An observation does not verify security, ownership or compliance, and InterfaceDelta assigns no scores or rankings. Methodology · Report an inaccuracy · Ask for removal

Identity and snapshot
Target key
sha256:91517554a759e256180acf3f71746a4fbbc51be01c68bcb3d683f7219f503004
Locator SHA-256
6746a3c2e1376624e9fbbabe95b802bfb987457ec7c9d7ed6c840a449ff35f37
Snapshot generated
4 Nov 2026, 07:02 UTC

The entry is one exact observed target, not a real-world service identity, and implies no ownership. Endpoint paths are not published; the locator hash lets an operator confirm their own URL.