DevGlobe
REMOTE · WWW.DEVGLOBE.DEV
The open-source talent graph for humans and AI agents. Find developers.
Available components
Last scanned (12 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 17 Oct 2026.
Category CRM and Sales
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security14
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 −18
The score moved with no change recorded against any check. We would rather say so than guess.
- 23 Oct 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 22 Oct 26 −18
The score moved with no change recorded against any check. We would rather say so than guess.
- 21 Oct 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Oct 26 −18
The score moved with no change recorded against any check. We would rather say so than guess.
- 18 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 14 Oct 26 0
- Stability: 0.97 → pass security
- 13 Oct 26 0
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Probed https://www.devglobe.dev/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of www.devglobe.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| devglobe.dev. | present | 31840 | 13 | Verified |
| www.devglobe.dev. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.devglobe.dev/mcp | Unreachable | ||
| http (plaintext) | http://www.devglobe.dev/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_similar_developers ~90
Use when the user wants alternatives similar to a known GitHub login. Similarity uses public repository, language, location, and profile signals and is not a suitability judgment. Example: {"login":"sajeetharan","limit":5}.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum similar profiles from 1 to 20 |
| login | string | yes | GitHub login of the source profile |
| Name | Type | Req | Description |
|---|---|---|---|
| methodologyDisclaimer | string | yes | – |
| resultCount | integer | yes | – |
| results | array | yes | – |
| source | string | yes | – |
No examples provided.
get_developer_profile ~62
Use when the user names a GitHub login or selects one DevGlobe search result and needs its public profile and contribution evidence. No authentication is required. Example: {"login":"sajeetharan"}.
| Name | Type | Req | Description |
|---|---|---|---|
| login | string | yes | GitHub login |
| Name | Type | Req | Description |
|---|---|---|---|
| methodologyDisclaimer | string | yes | – |
| profile | object | yes | – |
No examples provided.
get_introduction_status ~72
Use after request_introduction to check a request created by the same authenticated agent. An accepted request returns only the public GitHub contact route.
| Name | Type | Req | Description |
|---|---|---|---|
| developerLogin | string | yes | GitHub login used in the original request_introduction call |
| id | string | yes | Introduction request ID returned by request_introduction |
No output schema declared.
No examples provided.
get_trending_developers ~89
Use when recency or momentum matters. Lists public score gainers and high-ranking profiles new to impact tracking; do not use as a hiring recommendation. Example: {"days":30,"limit":10}.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Trend window from 1 to 90 days |
| limit | integer | – | Maximum gainers and new entries from 1 to 20 each |
| Name | Type | Req | Description |
|---|---|---|---|
| gainers | array | yes | – |
| generatedAt | string | – | – |
| hasHistory | boolean | yes | – |
| methodologyDisclaimer | string | yes | – |
| newEntries | array | yes | – |
| resultCount | integer | yes | – |
| windowDays | integer | yes | – |
No examples provided.
match_developers_to_repository ~103
Use when the user starts with a public GitHub repository and wants relevant indexed developers. Matches public owner, contribution, language, topic, repository, and self-declared opportunity signals; this is not a suitability judgment. Example: {"repository":"owner/repo","limit":10}.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum matches from 1 to 20 |
| repository | string | yes | Public GitHub repository as owner/repository or a github.com URL |
| Name | Type | Req | Description |
|---|---|---|---|
| methodologyDisclaimer | string | yes | – |
| repository | object | yes | – |
| resultCount | integer | yes | – |
| results | array | yes | – |
No examples provided.
preview_contribution_mission ~70
Use when the user wants one concrete open-source contribution opportunity for an indexed GitHub login. Read-only, rate limited, and does not reserve the issue. Example: {"login":"sajeetharan"}.
| Name | Type | Req | Description |
|---|---|---|---|
| login | string | yes | Public GitHub login already indexed by DevGlobe |
| Name | Type | Req | Description |
|---|---|---|---|
| mission | – | yes | – |
| profile | object | yes | – |
| reservationDisclaimer | string | yes | – |
| resultCount | integer | yes | – |
No examples provided.
request_introduction ~113
Use only after the user explicitly asks to contact an opted-in developer. Requires a bearer token, creates a consent-gated pending request, and never returns private contact details. Example: {"developerLogin":"octocat","reason":"We would like help maintaining our open-source React library.","project":"Example UI"}.
| Name | Type | Req | Description |
|---|---|---|---|
| developerLogin | string | yes | GitHub login selected by the user |
| project | string | yes | Project or organization name |
| reason | string | yes | Specific collaboration reason of at least 20 characters |
No output schema declared.
No examples provided.
search_developers ~189
Use when the user wants to find public developers by skill, name, language, location, agent availability, or active opportunity intent. Start discovery here; no authentication is required. Example: {"query":"TypeScript maintainers","location":"Germany","availableForAgents":true,"limit":5}.
| Name | Type | Req | Description |
|---|---|---|---|
| availableForAgents | boolean | – | Set true only when the user needs profiles accepting verified agent requests |
| language | string | – | Optional primary programming language, such as "TypeScript" |
| limit | integer | – | Maximum results from 1 to 20 |
| location | string | – | Optional public location text, such as "Germany" or "Colombo" |
| opportunityType | string | – | Optional active self-declared opportunity type; do not infer availability |
| query | string | yes | Required natural-language public search intent, such as "TypeScript maintainers" or a developer name |
| Name | Type | Req | Description |
|---|---|---|---|
| methodologyDisclaimer | string | yes | – |
| resultCount | integer | yes | – |
| results | array | yes | – |
No examples provided.
How do I install the DevGlobe MCP server?
DevGlobe is a hosted endpoint at https://www.devglobe.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.devglobe.dev
claude mcp add --transport http sajeetharan-devglobe 'https://www.devglobe.dev/mcp'
What is the DevGlobe MCP server?
DevGlobe is an MCP server listed in the public MCP registry as io.github.sajeetharan/devglobe. The open-source talent graph for humans and AI agents. Find developers. This page covers its hosted endpoint (https://www.devglobe.dev/mcp).
Is the DevGlobe MCP server safe to use?
DevGlobe scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the DevGlobe MCP server expose?
DevGlobe exposes 8 tools: search_developers, get_developer_profile, find_similar_developers, match_developers_to_repository, get_trending_developers, and 3 more. Their descriptions and schemas cost roughly 788 tokens of context every time the server is loaded.
Does the DevGlobe MCP server require authentication?
Its publisher declares no required credentials for DevGlobe. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the DevGlobe MCP server still maintained?
DevGlobe has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.