mcp.xynaptic

xynaptic-catalog

Xynaptic Catalog — access any of the 200+ Xynaptic services by name: bank analytics (bank-cashflow, bank-payment-risk), regional news, EU stocks, property rent/valuation, notam-area, AI agents, watches, storage. Pass {service, params} for GET services or {service, body} for POST ones; the x402 challenge is surfaced for payment. Usage: Use ONLY for a service outside the 23 flagship tools: bank analytics, regional news, EU stocks, property rent/valuation, notam-area, AI agents, watches, storage, skills. For flagship tools call them directly by name. Pass {service, params} — GET services — or {service, body} — POST services (ai-, insurance-, bank-*-parse, portfolio). [price: $0.000 per call, x402/USDC]

Input Schema

Name	Required	Description
`body`	No	JSON body for POST services (ai-, insurance-, bank-*-parse, portfolio-analysis, ticket-buy) — omit for GET services
`params`	No	query parameters for GET services, e.g. {siren: '552032534'} — omit for POST services
`service`	Yes	required. Xynaptic service name, e.g. bank-cashflow, news-eu, security-eu-price, property-rent, notam-area, ai-chat

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 4, 2026

addedInput schema / properties / body

Added value: +{
+  "description": "JSON body for POST services (ai-*, insurance-*, bank-*-parse, portfolio-analysis, ticket-buy) — omit for GET services",
+  "type": "object"
+}

changedInput schema / properties / params / description

Previous value: -"query parameters"New value: +"query parameters for GET services, e.g. {siren: '552032534'} — omit for POST services"

removedInput schema / properties / params / properties

Removed value: -{
-  "body": {
-    "description": "example: {\"transactions\":[]}",
-    "type": "string"
-  },
-  "params": {
-    "description": "example: {}",
-    "type": "string"
-  }
-}

removedInput schema / properties / params / required
```
Removed value: -[]
```

addedInput schema / properties / service

Added value: +{
+  "description": "required. Xynaptic service name, e.g. bank-cashflow, news-eu, security-eu-price, property-rent, notam-area, ai-chat",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "params"
-]New value: +[
+  "service"
+]

AddedOct 3, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does add real behavior: GET services take {service, params}, POST services take {service, body}, and 'the x402 challenge is surfaced for payment' tells the agent to expect a payment round-trip. It omits what happens after a challenge is satisfied (retry semantics) and the response shape, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core routing rule is front-loaded, which is good, but the GET/POST payload mapping is stated twice verbatim and the domain list is also duplicated between the opening and the usage sentence. The block is longer than it needs to be for the information conveyed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a gateway fronting 200+ services, the biggest missing piece is discovery: there is no mention of how an agent finds valid service names, so it must already know them (only three examples appear in the schema). Payment, mutation type, and payload shape are covered, but the naming/discovery gap is material.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the schema already states which service prefixes require body (ai-*, insurance-*, bank-*-parse, portfolio) and which take params. The description largely restates that mapping, adding no new syntax, naming conventions, or validation rules. Baseline 3 for a fully documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete verb+resource ('access any of the 200+ Xynaptic services by name') and enumerates the covered domains (bank analytics, regional news, EU stocks, property, notam, AI agents). It also explicitly frames itself as a fallback gateway rather than a peer of the flagship tools, so an agent can place it against the siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use ONLY for a service outside the 23 flagship tools' plus 'For flagship tools call them directly by name' gives a clear selection rule and an exclusion. However, it never names the 23 flagship tools, and the category list following 'flagship tools:' repeats the categories the catalog is supposed to cover, which blurs the boundary the agent needs to apply.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All mcp.xynaptic tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?