Tokenomic-Pulse MCP Server

by evozim Your server? Claim it

answering

Tokenomic-Pulse is answering right now. Last checked moments ago.

DeFi protocol simulation model scoring tokenomic structures.

Uptime history 47 days of history · worst day 99%

47 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

91 ms

Response time

average over 24h

authentication required

Access

sse

Nothing serious here today

Today is the operative word: we check Tokenomic-Pulse every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add tokenomic-pulse --transport http https://tokenomic-pulse-mcp.vercel.app/api/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "tokenomic-pulse": {
      "url": "https://tokenomic-pulse-mcp.vercel.app/api/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.tokenomic-pulse]
url = "https://tokenomic-pulse-mcp.vercel.app/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "tokenomic-pulse": {
      "url": "https://tokenomic-pulse-mcp.vercel.app/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "tokenomic-pulse": {
      "url": "https://tokenomic-pulse-mcp.vercel.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://tokenomic-pulse-mcp.vercel.app/api/mcp	sse	needs auth	64 ms	0 min ago

Alternatives to Tokenomic-Pulse

same job, measured the same way

Calculator MCP

by tech-sushant

A simple Model Context Protocol calculator server

28 installs/wk local only

CLIO Compression

by iowarp

Compression MCP server implementation using Model Context Protocol

local only

Deployhq MCP Server

by deployhq

Model Context Protocol (MCP) server for DeployHQ API integration

33 installs/wk local only

CLIO Arxiv

by iowarp

ArXiv MCP server implementation using Model Context Protocol

local only

MCP Aider Executor

by railkill

Model Context Protocol (MCP) server to execute aider-specific code editing operations

38 installs/wk local only

Kontra MCP

by bluwork

The Tenth Man Protocol — structured contrarian analysis for decision-makers via MCP

32 installs/wk local only

Nx MCP

by nrwl

A Model Context Protocol server implementation for Nx

57 193 installs/wk local only

Nx Console

by nrwl

A Model Context Protocol server implementation for Nx

local only

Tokenomic-Pulse — questions

Answers built from our own checks of this server.

Why is there no tool list for Tokenomic-Pulse?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Tokenomic-Pulse working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 91 ms. The bar chart above shows every period we have measured.

How do I connect Tokenomic-Pulse?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does Tokenomic-Pulse need an API key?

Yes. Every time we knock, Tokenomic-Pulse answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Tokenomic-Pulse?

It answers our handshake in 91 ms on average, which is faster than 84% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.