F
licenseA
qualityNot graded
maintenanceMCP server for Chainlink ecosystem monitoring with 6 tools: price feed tracking, VRF monitoring, automation status, CCIP tracking, and staking analytics. MIT licensed.
6
1
tenzro-chainlink
by xyz.tenzro
Server Details
Chainlink tools over MCP: CCIP cross-chain, data feeds, data streams, VRF, proof of reserve.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
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.
100% free. Your data is private.
Tool Definition Quality
A4/5.0
Tool DescriptionsA
Average 3.9/5 across 21 of 21 tools scored. Lowest: 3.2/5.
Server CoherenceA
Disambiguation5/5
All tools are grouped by service prefix (ccip_, chainlink_, ds_, por_, vrf_) and each has a unique purpose. For example, ccip_get_fee and ccip_send_message are clearly distinct, and even within similar functions like chainlink_get_price and ds_get_report, the descriptions clarify they target different data sources (on-chain feeds vs. low-latency streams). No overlap.
Naming Consistency5/5
Tool names follow a consistent pattern of service prefix + verb_noun (e.g., ccip_get_fee, ds_list_feeds, vrf_request_random). Even longer names like chainlink_broadcast_signed_tx adhere to the pattern. There is no mixing of cases or inconsistent verb forms.
Tool Count5/5
21 tools covering multiple Chainlink products (CCIP, Data Feeds, Data Streams, VRF, Functions, Automation, Proof of Reserve) is well-scoped. Each tool serves a distinct needed capability without bloat, and the count is within the ideal range for a focused integrated server.
Completeness4/5
The tool set covers core read and write operations for most services (e.g., full CCIP workflow from fee estimation to message sending and tracking). However, there are minor gaps: no tool to create or manage subscriptions (only get), and no direct Functions request execution (only cost estimation and subscription query). These are workable but not fully complete.
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.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables 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.
- FlicenseNot gradedqualityDmaintenanceMCP server providing agent-ready access to Chainlink's API for DeFi and crypto tools.
- AlicenseBqualityDmaintenanceAn 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.5147MIT