Is the Vercel Jestsprout Jestsprout MCP server down?

mcp-registry/app.vercel.jestsprout/jestsprout · v1.1.0

healthy
Last checked 2026-10-24 19:50 UTC · handshake 162ms

As of 2026-10-24 19:50 UTC, the Vercel Jestsprout Jestsprout MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
530
outages (90d)
0
tools
23

Solana rug checks, memecoin tools, swaps, and JestSprout Pay pages (Apple Pay, Solana Pay) + shop.

Install Vercel Jestsprout Jestsprout MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http vercel-jestsprout-jestsprout-mcp-server https://jestsprout.vercel.app/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "vercel-jestsprout-jestsprout-mcp-server": {
      "type": "http",
      "url": "https://jestsprout.vercel.app/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (88/100)

B (88/100): 0 error(s), 1 warning(s) across 23 tool(s); ~4,134 tokens of tool definitions.
Scores higher than 64% of 15,642 MCP servers Glimind has audited.
Its tool list costs an agent ~4,134 tokens per session — more than 55% of servers.
90 → 88 since 2026-10-22
no tool-poisoning patterns
Schemas100
Descriptions92
Safety hints84
Token cost100
Client compatibility70
Protocol40
Reliability100
Stability96

What to fix (5)

Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

2 tools share an identical description with another tool on this server.

Make each description say how the tool differs from its siblings, or the model will pick between them at random. How to fix →

Tools: bot_whoami, jestsprout_whoami

2 of 23 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: generate_coin_concept, generate_full_concept

In the last 30 days: 0 tool(s) removed and 1 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/app.vercel.jestsprout/jestsprout"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/app.vercel.jestsprout/jestsprout"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.vercel.jestsprout%2Fjestsprout.svg)](https://glimind.com/server/mcp-registry%2Fapp.vercel.jestsprout%2Fjestsprout?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fapp.vercel.jestsprout%2Fjestsprout?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.vercel.jestsprout%2Fjestsprout.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.vercel.jestsprout%2Fjestsprout.svg
   :target: https://glimind.com/server/mcp-registry%2Fapp.vercel.jestsprout%2Fjestsprout?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:06cbd2425aeef948…, first seen 2026-10-23, included at leaf 51488 of 60,876. Version history · verify what your client received.

Tools (23)

Compare: most reliable communication servers · most reliable other servers · most reliable knowledge servers · most reliable finance servers · most reliable media servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Vercel Jestsprout Jestsprout MCP server down right now?

As of 2026-10-24 19:50 UTC, the Vercel Jestsprout Jestsprout MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Vercel Jestsprout Jestsprout MCP server provide?

Vercel Jestsprout Jestsprout MCP server advertises 23 tools, including bot_dm_inbox, bot_dm_send, bot_hub_post, bot_hub_read, bot_hub_register.

How do I install Vercel Jestsprout Jestsprout MCP server?

Point your MCP client at this streamable-http endpoint: https://jestsprout.vercel.app/mcp

Is the Vercel Jestsprout Jestsprout MCP server safe to connect to an AI agent?

Glimind scanned all 23 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Vercel Jestsprout Jestsprout MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve