
Execute data-observability-mcp
io.github.EvozimPublished by GitHub account Evozimv2.0.0Updated Oct 24, 2026
Premium agentic endpoint for data-observability-mcp.
Overview
A remote MCP endpoint for data observability whose calls are paid per use through an x402 USDC settlement signature on Base Mainnet.
- What you can do
- Connects an assistant to a hosted data-observability endpoint over SSE so it can work with observability data through the server's tools, though no tool list is published in the manifest or description. Each request is settled on-chain through an x402 V2 payment flow on Base Mainnet. The endpoint is described only as a premium agentic endpoint, so the exact capabilities must be confirmed with the provider.
- When to use it
- Consider it when you want a hosted observability endpoint rather than running your own server, and you are set up to pay per request in USDC on Base Mainnet. It is not a good fit if you need a free, self-hosted, or clearly documented tool set.
- Requirements
- A remote SSE connection to the provider's endpoint. A Payment-Signature header carrying a Base64-encoded EIP-3009 TransferWithAuthorization signature for x402 V2 settlement on Base Mainnet, at $0.08 USDC per settlement. A wallet able to sign such authorizations and hold USDC on Base.
Installation
In SourceWeft
- Open Execute data-observability-mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via SSE. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.Evozim%2Fdata-observability-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"execute-data-observability": {
"type": "sse",
"url": "https://api.m2mcent.com/data-observability-mcp/sse"
}
}
}Tools
0Version history
1- v2.0.0LatestSep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.