mcp-registry/io.github.upforge-dev/upforge · v1.2.0
Verdict. Upforge Dev Upforge MCP server answered 99.97% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 1497 ms median handshake and 2 outages in 90 days. Its agent-readiness grade is A (91/100) across 20 tools, costing an agent about 4,795 tokens to load. Checked every few minutes; no tool is ever called.
Data as of .
| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.97% | 42% of MCP servers |
| Median handshake latency | 1497 ms | 10% of MCP servers |
| p95 handshake latency | 3810 ms | — |
| Checks in 30 days | 4,941 | — |
| Outages, 90 days | 2 | — |
| Median recovery | 6 min | — |
| Agent-readiness score | 91/100 (A) | 71% of MCP servers |
| Tools | 20 | — |
| Tool-list size for an agent | ~4,795 tokens | 39% of MCP servers |
| Days observed | 29 | — |
As of 2026-10-26 19:42 UTC, the Upforge Dev Upforge MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 6 minutes.
Explore Upforge services and evidence, or submit a prototype for a human-approved static fit check.
Claude Code
claude mcp add --transport http upforge-dev-upforge-mcp-server https://upforge.io/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"upforge-dev-upforge-mcp-server": {
"type": "http",
"url": "https://upforge.io/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
5 parameter(s) across 2 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. 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 →
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/io.github.upforge-dev/upforge"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.upforge-dev/upforge"}) over MCP.
book_consultation ~623 tokensfind_consultation_times ~474 tokenssubmit_project_review ~457 tokensrequest_consultation ~442 tokensask_echo ~423 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Fio.github.upforge-dev%2Fupforge?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.upforge-dev%2Fupforge?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.upforge-dev%2Fupforge.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.upforge-dev%2Fupforge.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.upforge-dev%2Fupforge?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:246ac24cdfbb4e28…, first seen 2026-10-17, included at leaf 507 of 75,084. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable calendar servers · most reliable security servers · most reliable retrieval servers · most reliable files servers
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.
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"
}
}
}
As of 2026-10-26 19:42 UTC, the Upforge Dev Upforge MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 6 minutes.
Upforge Dev Upforge MCP server advertises 20 tools, including ask_echo, book_consultation, check_service_area, finalize_review_upload, find_consultation_times.
Point your MCP client at this streamable-http endpoint: https://upforge.io/api/mcp
Glimind scanned all 20 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.
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.