mcp-registry/io.github.sajeetharan/devglobe · v1.6.0
As of 2026-10-18 00:07 UTC, the Sajeetharan Devglobe MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 97.7% of Glimind's liveness checks. It had 118 outages in 90 days, with a median recovery of 7 minutes.
The open-source talent graph for humans and AI agents. Find developers.
Point your MCP client at this streamable-http endpoint: https://www.devglobe.dev/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST.
Reachable 97.7% of the time over the last 30 days; median recovery 7 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
Handshake + tools/list takes ~2,279 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
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.
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.sajeetharan/devglobe"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.sajeetharan/devglobe"}) over MCP.
search_developers ~374 tokensrequest_introduction ~243 tokensget_introduction_status ~215 tokensmatch_developers_to_repository ~202 tokensfind_similar_developers ~174 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.sajeetharan%2Fdevglobe?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.sajeetharan%2Fdevglobe?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.sajeetharan%2Fdevglobe.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.sajeetharan%2Fdevglobe.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.sajeetharan%2Fdevglobe?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:373f48219a61da89…, first seen 2026-10-17, included at leaf 3539 of 19,761. Version history · verify what your client received.
Compare: most reliable retrieval servers · most reliable communication servers · most reliable code servers · most reliable search 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-18 00:07 UTC, the Sajeetharan Devglobe MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 97.7% of Glimind's liveness checks. It had 118 outages in 90 days, with a median recovery of 7 minutes.
Sajeetharan Devglobe MCP server advertises 8 tools, including find_similar_developers, get_developer_profile, get_introduction_status, get_trending_developers, match_developers_to_repository.
Point your MCP client at this streamable-http endpoint: https://www.devglobe.dev/mcp
Glimind scanned all 8 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.