DevGlobe
REMOTE · WWW.DEVGLOBE.DEV · SCANNED SEP 20
The open-source talent graph for humans and AI agents. Find developers.
Available components
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 Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 903 tokens (~100/item across 9 items; 8 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
- Structured output schemas are declared (75% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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'
{
"mcpServers": {
"sajeetharan-devglobe": {
"url": "https://www.devglobe.dev/mcp"
}
}
} {
"servers": {
"sajeetharan-devglobe": {
"type": "http",
"url": "https://www.devglobe.dev/mcp"
}
}
} [mcp_servers.sajeetharan-devglobe] url = "https://www.devglobe.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sajeetharan-devglobe": {
"type": "remote",
"url": "https://www.devglobe.dev/mcp",
"enabled": true
}
}
} openclaw mcp add sajeetharan-devglobe --url 'https://www.devglobe.dev/mcp' --transport streamable-http
mcp_servers:
sajeetharan-devglobe:
url: "https://www.devglobe.dev/mcp" {
"McpServers": {
"sajeetharan-devglobe": {
"Transport": "http",
"Url": "https://www.devglobe.dev/mcp"
}
}
} assistant mcp add sajeetharan-devglobe -t streamable-http -u 'https://www.devglobe.dev/mcp'
{
"mcpServers": {
"sajeetharan-devglobe": {
"type": "http",
"url": "https://www.devglobe.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → partial ▲ security
- DNSSEC: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.60 ▲ functional
- 13 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.53 → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- DNSSEC: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 12 Sept 26 +2
- DNSSEC: fail → pass ▲ security
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 11 Sept 26 −1
- DNSSEC: pass → fail ▼ security
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- New prompt “quick-start” functional
- Server version: 1.5.1 → 1.6.0 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 20 Sept 2026 · Probed https://www.devglobe.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.devglobe.dev | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 19 Aug 2026 | 19 Feb 2027 | RSA 2048 | SHA256-RSA | 133d39c39d0a4736df5c75506ba6380 |
| SANs: www.devglobe.dev | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
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 No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
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 | Verified | 200 | |
| http (plaintext) | http://www.devglobe.dev/mcp | HTTPS enforced | 301 | https://www.devglobe.dev/mcp |
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 ~53
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 | – |
| id | string | yes | – |
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.
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 85 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 769 tokens of context every time the server is loaded.
Does the DevGlobe MCP server require authentication?
No. We connected to DevGlobe without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DevGlobe MCP server still maintained?
DevGlobe is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.