ToolsMCP
uetr.ai - UETR and SWIFT Payment Tracking
Listed in the official MCP Registry with a hosted streamable-http endpoint. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- uetr.ai
- Prerequisites
- An MCP client that supports streamable-http. No credential header is declared in the registry record.
- Current version
- 1.0.1-registry.1 · updated
- Official links
Publisher’s description
UETR tracking and SWIFT payment tracking for AI apps. Read transfer status and manage monitoring.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 1.0.1-registry.1, registry status active. 1 remote endpoint (streamable-http)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- uetr.ai
- Version observed
- 1.0.1-registry.1
- Source
- registry.modelcontextprotocol.io/v0.1/servers/ai.uetr%2Fuetr.ai/versions/1.0.1-registry.1
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Create invoices and handle payments | Publisher description mentions “payment”, “manage”. | No connection check or task run. Capability is as described by the publisher. | Rule payments-invoices matched: “payment”, “manage”. Rule payments-invoices. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Remote endpoints
https://uetr.ai/mcp(streamable-http)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
ai.uetr/uetr.ai
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.