Talandor
Public MCP report

Bea Gov

https://gateway.pipeworx.io/bea-gov/mcp

Official Registry

Official Registry · io.github.pipeworx-io/bea-gov · Publisher namespace: io.github.pipeworx-io

Server checked today at 20:40 UTC

Tools were not executed.

Insufficient evidence

What Talandor observed

Insufficient public evidence

Incomplete observation

Insufficient evidence is a limit of this public check, not a judgment that the server is unusable. Retry later. Public tools were not fully observable.

https://gateway.pipeworx.io/bea-gov/mcp
AvailabilityIncomplete observationmeasured
ToolsNot fully observablemeasured
CompatibilityUnknownunknown

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.
    Client setup cannot be inferred yet. This public check did not observe a complete tool contract or an authentication challenge, so there is no honest compatibility signal.
    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
    No earlier complete public snapshot yet. Watch would start a baseline on the next complete check.
    
      
    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.
    Tools are not observable for this result. A private catalog is not published. This is not a claim that the server has no tools.
    
      
    Evidence and limitations
    Method: anonymous Streamable HTTP probe. We never invoke a tool.
    Attempted protocols: 2026-07-28, 2025-11-25
    ProtocolNot listed in this check
    TransportHTTPS · HTTP 429
    AuthNo authentication challenge in this check
    EvidenceTransport only
    Total latency510 ms
    Response bytes0
    MCP_RESPONSE_ERROR — The endpoint returned an incomplete or incompatible MCP response.
    
      
    Observation history
    Unknown
     · stable since 
    No protocol · no change · 45 checks
    No snapshots have been stored yet.
    
      
    Deep monitoring eligibility
    Not eligible yet
    Only transport-level evidence was observed; no public tools/list contract was confirmed.
    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.