Skip to main content
Glama

Tenzro Chainlink MCP

by network.tenzro
OverviewDiscussionsAdmin

Server Details

Chainlink MCP: CCIP, CCT pools, Data Feeds, Data Streams, VRF v2.5, PoR, Automation, Functions.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over 43 days
Last Tested
Transport
Streamable HTTP
URL
Repository
tenzro/tenzro-network
GitHub Stars
0

TDQS

A4/5.0

Scored across 21 tools

Disambiguation5/5

Each tool has a distinct purpose, clearly grouped by prefix (ccip_, chainlink_, ds_, por_, vrf_). Within each group, tools like ccip_get_fee, ccip_send_message, and ccip_track_message are unambiguous. No overlapping functionality.

Naming Consistency5/5

All tools follow a consistent prefix_action_noun pattern in snake_case (e.g., ccip_get_fee, chainlink_list_feeds, ds_get_report). No mixing of conventions like camelCase or inconsistent verb forms.

Tool Count5/5

21 tools cover multiple Chainlink products (CCIP, Data Feeds, Data Streams, Proof of Reserve, VRF, Automation, Functions) appropriately. Each product has 2-8 dedicated tools, making the set well-scoped without being overwhelming or thin.

Completeness4/5

Read operations are comprehensive for all products. The generic chainlink_broadcast_signed_tx covers writes. Minor gaps exist like missing subscription management for VRF/Functions, but core workflows are covered.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 21 tool updates
    • Changedccip_get_fee1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedccip_get_lanes1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedccip_get_rate_limits1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedccip_get_supported_chains1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedccip_get_supported_tokens1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedccip_get_token_pool1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedccip_send_message1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedccip_track_message1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedchainlink_broadcast_signed_tx1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedchainlink_check_upkeep1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedchainlink_estimate_functions_cost1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedchainlink_get_price1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedchainlink_get_subscription1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedchainlink_get_upkeep_info1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedchainlink_list_feeds1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedds_get_report1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedds_list_feeds1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedpor_get_reserve1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedpor_list_feeds1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedvrf_get_subscription1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
    • Changedvrf_request_random1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "description": "Generic passthrough envelope for MCP tools that surface arbitrary\nJSON returned by the underlying JSON-RPC layer or upstream HTTP API.\n\nPer the MCP 2025-06-18 spec, every `#[tool]` handler must return a\nschema-bearing typed value so the rmcp router can populate\n`outputSchema` on `tools/list` and emit `structuredContent` on\n`tools/call`. For tools whose underlying response shape is determined\nby an external surface (the Tenzro JSON-RPC dispatcher, an L1\nblockchain RPC, or a SaaS API), `RpcPassthroughOutput` carries the\nraw `serde_json::Value` verbatim under a single `result` field.\n\nTools with a stable, fully-typed response shape (e.g. `get_balance`,\n`create_wallet`) define their own dedicated `*Output` struct instead.",
+  "properties": {
+    "result": {
+      "description": "Underlying response payload verbatim."
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "RpcPassthroughOutput",
+  "type": "object"
+}
  2. 1 tool update
    • Addedchainlink_broadcast_signed_tx
  3. 20 tool updates
    • First observedccip_get_fee
    • First observedccip_get_lanes
    • First observedccip_get_rate_limits
    • First observedccip_get_supported_chains
    • First observedccip_get_supported_tokens
    • First observedccip_get_token_pool
    • First observedccip_send_message
    • First observedccip_track_message
    • First observedchainlink_check_upkeep
    • First observedchainlink_estimate_functions_cost
    • First observedchainlink_get_price
    • First observedchainlink_get_subscription
    • First observedchainlink_get_upkeep_info
    • First observedchainlink_list_feeds
    • First observedds_get_report
    • First observedds_list_feeds
    • First observedpor_get_reserve
    • First observedpor_list_feeds
    • First observedvrf_get_subscription
    • First observedvrf_request_random

Related MCP Connectors

Related MCP Servers

  • chainlink-sentinel

    ElromEvedElElyon
    F
    license
    A
    quality
    Not graded
    maintenance
    MCP server for Chainlink ecosystem monitoring with 6 tools: price feed tracking, VRF monitoring, automation status, CCIP tracking, and staking analytics. MIT licensed.
    6
    1
    -

  • Chainlink MCP Server

    goldk3y
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables interaction with Chainlink's decentralized oracle network, providing access to real-time price feeds, serverless functions, smart contract automation, verifiable randomness, cross-chain messaging, and proof of reserve across multiple blockchain networks.
    -

  • chainlink-feeds-mcp

    kukapay
    A
    license
    B
    quality
    D
    maintenance
    An MCP server that provides real-time access to Chainlink's decentralized on-chain price feeds, optimized for seamless integration into AI agents and autonomous systems.
    5
    4 npm
    7
    MIT

  • Chainlink MCP Server

    junct-bot
    F
    license
    Not graded
    quality
    D
    maintenance
    MCP server providing agent-ready access to Chainlink's API for DeFi and crypto tools.
    -
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources