Talandor
Public MCP report

Affiliate Networks MCP

https://mcp.agenticaffiliate.ai/mcp

Official Registry

Official Registry · ai.agenticaffiliate/affiliate-networks-mcp · Publisher: ai.agenticaffiliate

Last observed

Degraded
Can I use it?

The endpoint responded with limited evidence

Review the diagnostic below and retry later. One or more non-essential checks were incomplete, so this is not a complete public contract.

https://mcp.agenticaffiliate.ai/mcp
ToolsNot observable
AuthNot observed
ProtocolNot observed
TransportNot qualified
Evidence completenessTransport only
Latency1076 ms

Setup guidance

Compatibility is inferred from published configuration rules and is not manually verified in each client.

Show client compatibility details
Claude
No protocol version observed.
Not verified
Cursor
Streamable HTTP and public HTTPS were observed.
Not verified
ChatGPT
A public contract was not fully observed.
Not verified
VS Code
Public remote HTTP configuration can be assessed.
Not verified
Generic MCP
No protocol version observed.
Not verified

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

What changed

A prior observation exists, but a complete contract diff is not available.

No prior complete snapshot is available for a contract diff.

Evidence and limitations

Method: anonymous Streamable HTTP probe. We never invoke a tool.

Attempted protocols: 2026-07-28

ProtocolNot observed
TransportNot qualified
AuthNot observed
EvidenceTransport only
Total latency1076 ms
Response bytes0

MCP_RESPONSE_ERROR — The endpoint returned an incomplete or incompatible MCP response.

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. This is not a claim that the server has no tools.

How to use this MCP

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

Choose your client below, then copy the endpoint or configuration. Authentication is completed with the MCP provider, never inside Talandor.

Open the official client guide (opens in a new tab)

      
Observation history
Degraded
No protocol
Reachable · auth required
2026-07-28
Reachable · auth required
2026-07-28
Reachable · auth required
2026-07-28
Reachable · auth required
2026-07-28
Reachable · auth required
2026-07-28
Reachable · auth required
2026-07-28
Reachable · auth required
2026-07-28
Reachable · auth required
2026-07-28
Reachable · auth required
2026-07-28
Reachable · auth required
2026-07-28
Reachable · auth required
2026-07-28
Reachable · auth required
2026-07-28
Reachable · auth required
2026-07-28
Reachable · auth required
2026-07-28
Reachable · auth required
2026-07-28
Reachable · auth required
2026-07-28
Reachable · auth required
2026-07-28
Reachable · auth required
2026-07-28
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 monitoring and alerts are coming soon. This report does not create a watch, payment or external email.
See public monitoring

      
Watch · 9 €/month
Watch is not available for this evidence
This result is transport only. A Watch needs a complete public contract or a qualified authentication surface before it can monitor meaningful changes.
Full WatchAvailability, protocol, auth and public tool contract changes
Surface WatchAvailability, TLS, protocol and auth surface — no private tool diff
Watch is not open in this deployment: no payment, account or external email is created from this page.
See Watch coverage and status