Talandor
Public MCP report

JackTrade CRM

https://frostsa2.ed1.jacktrade.xyz/jacktrade/mcp_api/v1/message

Official Registry

Official Registry · co.jacktrade/jacktrade-crm · Publisher namespace: co.jacktrade

Server checked today at 22:53 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://frostsa2.ed1.jacktrade.xyz/jacktrade/mcp_api/v1/message
AvailabilityReachablemeasured
ToolsPrivate until you sign in · not verifiedmeasured
Assistant testNot testable before 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)
    
      
    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: https://frostsa2.ed1.jacktrade.xyz
    Protocol2026-07-28
    TransportStreamable HTTP
    AuthRequired · challenge observed
    EvidenceAuthentication surface observed
    Total latency766 ms
    Response bytes345
    AUTH_REQUIRED — The endpoint requires authentication; no credentials were used.
    AUTH_CHALLENGE_MISSING — The endpoint requested authentication without publishing a complete challenge.
    
      
    Observation history
    Reachable · auth required
     · stable since 
    2026-07-28 · no change · 85 checks
    Reachable · auth required
    2026-07-28
    Reachable · auth required
    2026-07-28
    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.
    A Watch starts from the payment section on this page, and only after a verified payment.
    See public monitoring
    
      
    
      
    Watch · recurring plan
    Watch this MCP
    Your agent depends on this MCP. When Watch is active, periodic checks alert you when we observe a change that may affect the client you selected.
    • Know when it goes downWhen Watch is active, availability is observed about every 5 minutes. An outage is confirmed after two failed checks, so a single miss is not treated as a lasting outage.
    • Know when its contract changesDeep checks about every hour compare public tool catalogs and authentication surfaces over time.
    • Know what changed and what to fixAn alert names the observed change and the next step for the client you selected.
    Authentication-surface coverage: Availability, TLS, protocol and public authentication-surface changes can be compared; private tools are not included.
    Full WatchAvailability, protocol, auth and public tool contract changes
    Surface WatchAvailability, TLS, protocol and auth surface — no private tool diff
    Early access currently activates this first endpoint; adding more endpoints up to the planned limit of five is not open in this deployment. Live checkout is open. A Watch activates only after a verified payment event; a browser return never starts monitoring.
    Start Watch