Talandor
Public MCP report

APISign

https://apisign.io/mcp

Official Registry

Official Registry · io.apisign/apisign · Publisher namespace: io.apisign

Server checked today at 20:19 UTC

Tools were not executed.

Reachable · sign-in required

What Talandor observed

Sign-in required

Reachable

The server answered, but asks you to sign in inside your assistant. Private tools were not verified. Talandor never collects credentials.

https://apisign.io/mcp
AvailabilityReachablemeasured
ToolsPrivate until you sign in · not verifiedmeasured
CompatibilityUnknown until you sign inunknown

Configure your assistant · Check details

How to use this MCP

Talandor checks the server; it does not connect the server to your assistant.

Choose your assistant, then copy the configuration shown for that client. Authentication is completed with the MCP provider, never inside Talandor.

    Open the official client guide (opens in a new tab)
    Compatibility evidence by assistant
    Compatibility is estimated from published configuration rules and is not a hands-on test in each client.
    Claude
    This public check is complete. Sign in inside this client; Talandor never collects credentials.
    Sign-in in client
    Cursor
    This public check is complete. Sign in inside this client; Talandor never collects credentials.
    Sign-in in client
    ChatGPT
    This public check is complete. Sign in inside this client; Talandor never collects credentials.
    Sign-in in client
    VS Code
    This public check is complete. Sign in inside this client; Talandor never collects credentials.
    Sign-in in client
    Generic MCP
    This public check is complete. Sign in inside this client; Talandor never collects credentials.
    Sign-in in client
    Rule evidence: Remote HTTPS rule v0.2 · reviewed 2026-09-12 · Remote HTTP rule v0.2 · reviewed 2026-09-12 · Remote app rule v0.2 · reviewed 2026-09-12 · Protocol and transport rule v0.2 · reviewed 2026-09-12
    
      
    Check details
      
    What changed
    This public check is complete. There is no public tools contract to diff. Surface Watch can follow the authentication challenge.
    
      
    Server-provided content. Tool names, descriptions and schemas below are copied from the MCP server. They may be in another language. Talandor does not translate or verify them.
    Tools and declared exposure
    Server annotations are declarations, not verified behavior.
    This public check is complete. Tools stay private until you sign in in a client. Talandor never collects credentials.
    
      
    Evidence and limitations
    Method: anonymous Streamable HTTP probe. We never invoke a tool.
    Attempted protocols: 2026-07-28
    OAuth metadata: not announced
    Protocol2026-07-28
    TransportStreamable HTTP
    AuthRequired · challenge observed
    EvidenceTransport only
    Total latency3625 ms
    Response bytes27454
    AUTH_REQUIRED — The endpoint requires authentication; no credentials were used.
    AUTH_CHALLENGE_MISSING — The endpoint requested authentication without publishing a complete challenge.
    AUTH_METADATA_UNAVAILABLE — Authentication metadata was not available for inspection.
    
      
    Observation history
    Reachable · auth required
     · stable since 
    2026-07-28 · no change · 54 checks
    No snapshots have been stored yet.
    
      
    Deep monitoring eligibility
    Surface Watch eligible
    This authentication-surface result is a complete public check. Deep tool-contract diffs need a public tools/list; Surface Watch can follow the sign-in challenge.
    Personal Watch is not open yet. This report does not start a Watch or a payment.
    See public monitoring
    
      
    
      
    Automatic monitoring later
    Saving this connector does not start a Watch. Watch is a future offer; subscriptions and alerts are not available yet.
    This result is not eligible for automatic monitoring yet.