FeedOracle Trust Layer - 10-tool cross-server trust: signing, anchoring, verification.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 3.8/5 across 10 of 10 tools scored.
Each tool addresses a distinct aspect of the trust layer: reputation, confidence gating, evidence anchoring, freshness, signed facts, hallucination detection, provenance, infrastructure status, claim verification, and signature verification. There is no ambiguity between them.
All tool names use snake_case, which is consistent, but the verb usage varies (e.g., 'get_signed_fact', 'verify_claim', 'trust_status'). While readable, a uniform verb_noun pattern (e.g., all starting with verbs) would improve predictability.
With 10 tools, the server is well-scoped for a trust layer. Each tool provides a necessary function without redundancy, balancing coverage and simplicity.
The tool set covers core trust operations: reputation, confidence, evidence anchoring, freshness, verification, and provenance. Minor gaps exist, such as the absence of tools for updating or revoking anchored evidence, but the surface is largely complete for its domain.
agent_reputationInspectGet trust score and reputation for an AI agent from FeedOracle KYA (Know Your Agent) system. Returns trust level (UNVERIFIED → CERTIFIED), score (0-100), and registration details.
| Name | Required | Description | Default |
|---|---|---|---|
| client_id | No | Agent's client_id from KYA registration | |
| agent_name | No | Agent name to search (if client_id unknown) |
confidence_gateInspectDecision gate for agents: should I proceed, exercise caution, abstain, or escalate? Evaluates multi-factor confidence for a specific action type (cite, trade, report, recommend) against a threshold.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Token to evaluate | |
| action_type | No | What the agent wants to do: cite, trade, report, recommend | cite |
| min_confidence | No | Minimum confidence to proceed (0-100, default: 70) |
evidence_anchorInspectAnchor a fact on-chain (Polygon) as immutable, timestamped evidence. Creates an append-only registry entry with pack_id and content hash. Tamper-proof audit trail.
| Name | Required | Description | Default |
|---|---|---|---|
| fact | Yes | The fact to anchor | |
| symbol | No | Related token symbol (optional) | |
| framework | No | Framework context: trust_layer, mica, dora | trust_layer |
freshness_guardInspectCheck if data is current, stale, or expired. Prevents agent decisions based on outdated information. Configurable max age threshold.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | No | Token symbol (optional — checks overall feed if omitted) | |
| max_age_seconds | No | Maximum acceptable age in seconds (default: 300) |
get_signed_factInspectGet a cryptographically signed, machine-verifiable fact. Returns ES256K-signed data with JWKS verification URL. Other agents can independently verify the signature.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Token symbol: USDC, RLUSD, EURC, USDT, DAI | |
| fact_type | No | Type: price, peg, market_cap, reserve | price |
hallucination_checkInspectCompare an agent's statement against ground truth evidence. Detects factual mismatches and dangerous hallucination patterns (absolute language, suspect claims). Returns evidence checks and red flags.
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | Optional context for the statement | |
| statement | Yes | The statement to check against evidence |
provenance_traceInspectFull data provenance chain — traces every data point from external source (CoinGecko, ESMA, on-chain) through FeedOracle processing to final delivery. Each step individually hashed. Supports EU AI Act Art. 13 transparency requirements.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes | Token symbol to trace |
trust_statusInspectTrust Layer infrastructure health, capabilities, and component status. Shows which verification services are online and what the Trust Layer can do.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
verify_claimInspectVerify an agent's claim against FeedOracle signed evidence. Checks if a statement (e.g. 'USDC market cap is $32B') matches live, cryptographically signed data. Returns verified/partially_verified/unverified with confidence score and recommended action.
| Name | Required | Description | Default |
|---|---|---|---|
| claim | Yes | The claim to verify, e.g. 'USDC has $32B market cap' | |
| symbol | No | Token symbol (auto-detected from claim if omitted) |
verify_signatureInspectVerify a JWS or DSSE signature from FeedOracle evidence. Confirms cryptographic integrity and origin authenticity. Public JWKS at /.well-known/jwks.json.
| Name | Required | Description | Default |
|---|---|---|---|
| jws | No | JWS token to verify | |
| content_hash | No | Content hash to verify (sha256:...) |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
