DevMatch
REMOTE · MCP.DEV-MATCH.XYZ · SCANNED SEP 20
DevMatch — evidence-based engineer hiring for mission-driven teams.
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 Security86
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability74
- 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
- Context-footprint check failed: tool/resource definitions use about 2256 tokens (~564/item across 4 items; 3 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities73
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.Pass
Unverified: 1 category
A category scored 0 because we couldn't verify past authentication. We only credit what we can confirm, so an authenticated endpoint we can't read counts against the score. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the DevMatch MCP server?
DevMatch is a hosted endpoint at https://mcp.dev-match.xyz/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 · mcp.dev-match.xyz
claude mcp add --transport http luca-blight-devmatch 'https://mcp.dev-match.xyz/mcp'
{
"mcpServers": {
"luca-blight-devmatch": {
"url": "https://mcp.dev-match.xyz/mcp"
}
}
} {
"servers": {
"luca-blight-devmatch": {
"type": "http",
"url": "https://mcp.dev-match.xyz/mcp"
}
}
} [mcp_servers.luca-blight-devmatch] url = "https://mcp.dev-match.xyz/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"luca-blight-devmatch": {
"type": "remote",
"url": "https://mcp.dev-match.xyz/mcp",
"enabled": true
}
}
} openclaw mcp add luca-blight-devmatch --url 'https://mcp.dev-match.xyz/mcp' --transport streamable-http
mcp_servers:
luca-blight-devmatch:
url: "https://mcp.dev-match.xyz/mcp" {
"McpServers": {
"luca-blight-devmatch": {
"Transport": "http",
"Url": "https://mcp.dev-match.xyz/mcp"
}
}
} assistant mcp add luca-blight-devmatch -t streamable-http -u 'https://mcp.dev-match.xyz/mcp'
{
"mcpServers": {
"luca-blight-devmatch": {
"type": "http",
"url": "https://mcp.dev-match.xyz/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.
- 16 Sept 26 +2
- DNSSEC: fail → pass ▲ security
- 6 Sept 26 0
- Stability: 0.97 → pass security
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_similar_projects” rewrote its description, which is the text the model reads security
- Tool “find_candidates” rewrote its description, which is the text the model reads security
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Aug 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.
- 28 Aug 26 +8
- Judged manipulation: unverified → pass ▲ security
- Schema quality: unverified → excellent ▲ functional
- 27 Aug 26 −7
- Judged manipulation: pass → unverified ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_candidates” rewrote its description, which is the text the model reads security
- Schema quality: excellent → unverified ▼ functional
- “find_candidates” reworded the description of “limit” cosmetic
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://mcp.dev-match.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.dev-match.xyz | CN=WE1,O=Google Trust Services,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | eedf660c434a734513a74ced888ec01d |
| SANs: mcp.dev-match.xyz | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.dev-match.xyz. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| dev-match.xyz. | present | 21407 | 8 | Verified |
| mcp.dev-match.xyz. | Verified address RRset verified with the apex keys |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.dev-match.xyz/mcp | Auth required | 401 | |
| http (plaintext) | http://mcp.dev-match.xyz/mcp | HTTPS enforced | 301 | https://mcp.dev-match.xyz/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_candidates ~661
Find engineers who uniquely fit a role or project from open-source contributions and other public work, with evidence. Input: pass the richest context you have — (1) a full job description (most common), (2) a synthesized brief after reviewing a company's public repo (README + stack + role needs — preferred over a bare URL when you've evaluated the project), (3) a public github.com repo URL (server fetches README/topics; private repos → paste README as text), or (4) an informal role brief. Longer, more specific input produces a tighter mission fit. Optional `location` narrows to a city, country, or ISO country code. Returns up to limit candidates (default 20, max 20) with full inline profiles in structuredContent (view=candidates): login, name, bio, location, followers, reach (cross-platform audience percentile + reach), html_url, top_repos, signals, matched_projects, location_match, and contact (top_topics / top_domains / top_languages / top_subtopics are optional until software-topic backfill). Results never include bots, CI, or service accounts — they are filtered out automatically. Use the optional `exclude` array (GitHub logins or org names) to drop additional accounts. AGENT MODE: consume structuredContent only. HUMAN MODE: MCP App panel shows candidate cards; use server instructions for text-only hosts. Do not call get_profile for handles already in these results unless the user asks for deeper detail. Defense (SBIR), NRC filings, and mining QP consents are matched by lexical FTS over award titles, accessions, and consent letters — not abstract similarity. Publication, NTRS, repo, and TechPort roles still use description vectors. Do not claim a semantic abstract match for an NRC accession or a QP consent.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude | array | – | Optional. GitHub logins or org names to exclude from results (case-insensitive). Matches a candidate's login AND the owner/org of every repo they matched on — so passing a company's GitHub org (e.g.… |
| input | string | yes | Search brief: full JD, repo-derived summary (preferred when you've reviewed the project), README excerpt, informal role brief, or a PUBLIC github.com repo URL. Private repos: paste README content as… |
| limit | integer | – | Max candidates to return. Default 20, max 20. |
| location | string | – | Optional. Restrict results to a place — a city ("Bozeman"), US state ("MT" / "Montana"), country name ("Germany"), or ISO country code ("US"). Matched against the candidate's stated and normalized lo… |
| Name | Type | Req | Description |
|---|---|---|---|
| cache_source | string | – | hit=fresh cache; miss=live retrieval; stale=last known-good shortlist after the engine timed out or was unavailable (degraded=true). |
| candidates | array | yes | Shortlist of engineers who uniquely fit the role, with evidence. When presenting to the user, format each item using FindCandidatesPresentationTemplate from server instructions — list every contact.u… |
| degrade_reason | string | – | Why degraded is true: embedding/FTS fallback, upstream_timeout / upstream_unreachable with cache_source=stale, or discovery_fallback. |
| degraded | boolean | – | True when this shortlist is not full quality: FTS-only retrieval, last-known-good (cache_source=stale), or discovery corpus fallback. Hosts should say so; do not invent extra candidates. |
| discovery_fallback | boolean | – | True when auto mode fell back from work_artifacts to serving.projects because searchable embedding coverage was below threshold. Explicit env overrides are not fallbacks. |
| discovery_source | string | – | Which software repository index supplied GitHub candidates: work_artifacts (artifact-first) or serving.projects (legacy). Omitted when the query did not use the GitHub software lane. |
| precision_gate | string | – | Whether the LLM precision screen ran on this response. "on" means results were filtered for relevance; "off" means raw retrieval order. When the screen was requested but unavailable, the tool returns… |
| query_ms | integer | – | End-to-end query time in milliseconds |
| total_count | integer | yes | Count of candidates returned (≤ requested limit) |
| view | string | – | Payload discriminator for MCP App hosts |
No examples provided.
find_similar_projects ~141
Find open-source projects similar to a seed GitHub repo, closest in description, topics, and README. Each result includes top contributors as leads — not a hiring shortlist. Returns structuredContent (view=similar_projects). Agents: consume structuredContent only. Use for landscape mapping or to discover anchor repos; follow with find_candidates for hiring matches.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Number of similar projects to return. Defaults to 10, max 25. |
| repo | string | yes | Seed repo in `owner/name` form (e.g. 'karpathy/llm.c'). A full github.com URL is also accepted; the server strips the prefix. |
| Name | Type | Req | Description |
|---|---|---|---|
| cache_source | string | – | – |
| projects | array | yes | Similar projects, closest to the seed repo by vector similarity. |
| query_ms | integer | – | – |
| seed | string | – | The owner/name searched against |
| total_count | integer | – | – |
No examples provided.
get_profile ~254
Fetch one contributor's profile card by GitHub login, ORCID iD (or orcid.org URL), or a find_candidates `id` (source:name such as ntrs:Ada Lovelace). Do not invent a GitHub handle for research or deep-tech people — pass their id. find_candidates already returns full inline profiles; use get_profile only for ids outside those results or when the user asks for deeper detail. Returns structuredContent (view=profile). Agents: consume structuredContent only. IMPORTANT — interpreting recent_activities: indexed GitHub activity in the current ingestion window (2025–2026), up to ~20 events per recent project. NOT a complete career history. Empty or older activity does not mean inactive.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Person to look up: a GitHub login (no '@'), an ORCID iD or https://orcid.org/<id> URL, or a find_candidates id (source:name such as ntrs:Ada Lovelace). Do not invent a GitHub handle for research or d… |
| id | string | – | Alias for handle. Pass a find_candidates `id` (GitHub login, ORCID iD, or source:name). |
| Name | Type | Req | Description |
|---|---|---|---|
| avatar_url | string | – | – |
| bio | string | – | – |
| company | string | – | – |
| display_name | string | – | – |
| string | – | – | |
| followers | integer | – | – |
| html_url | string | – | Profile URL (GitHub or https://orcid.org/<id>) |
| location | string | – | – |
| login_name | string | yes | GitHub handle. Empty for ORCID and source:name people — use person_id. |
| name | string | – | – |
| person_id | string | – | Stable lookup key: GitHub login, ORCID iD, or source:name. |
| profile_readme | string | – | User's profile README content if present |
| public_repos | integer | – | – |
| recent_activities | array | – | Indexed GitHub events from current ingestion window (2025–2026). NOT a full career timeline. |
| social_accounts | object | – | Social URLs (twitter, linkedin, etc.) |
| top_projects | array | – | Highest-contribution projects this user worked on |
No examples provided.
What is the DevMatch MCP server?
DevMatch is an MCP server listed in the public MCP registry as io.github.Luca-Blight/devmatch. DevMatch, evidence-based engineer hiring for mission-driven teams. This page covers its hosted endpoint (https://mcp.dev-match.xyz/mcp).
Is the DevMatch MCP server safe to use?
DevMatch scores 79 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 DevMatch MCP server expose?
DevMatch exposes 3 tools: find_candidates, get_profile, find_similar_projects. Their descriptions and schemas cost roughly 1,056 tokens of context every time the server is loaded.
Does the DevMatch MCP server require authentication?
Yes. DevMatch asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the DevMatch MCP server still maintained?
DevMatch 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.