DevRel Directory
REMOTE · DEVREL.DIRECTORY · SCANNED SEP 22
Search DevRel tools, communities, jobs, events, CFPs, and guides from devrel.directory.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 870 tokens (~145/item across 6 items; 6 tools + 0 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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 DevRel Directory MCP server?
DevRel Directory is a hosted endpoint at https://devrel.directory/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 · devrel.directory
claude mcp add --transport http directory-devrel-devrel-directory 'https://devrel.directory/mcp'
{
"mcpServers": {
"directory-devrel-devrel-directory": {
"url": "https://devrel.directory/mcp"
}
}
} {
"servers": {
"directory-devrel-devrel-directory": {
"type": "http",
"url": "https://devrel.directory/mcp"
}
}
} [mcp_servers.directory-devrel-devrel-directory] url = "https://devrel.directory/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"directory-devrel-devrel-directory": {
"type": "remote",
"url": "https://devrel.directory/mcp",
"enabled": true
}
}
} openclaw mcp add directory-devrel-devrel-directory --url 'https://devrel.directory/mcp' --transport streamable-http
mcp_servers:
directory-devrel-devrel-directory:
url: "https://devrel.directory/mcp" {
"McpServers": {
"directory-devrel-devrel-directory": {
"Transport": "http",
"Url": "https://devrel.directory/mcp"
}
}
} assistant mcp add directory-devrel-devrel-directory -t streamable-http -u 'https://devrel.directory/mcp'
{
"mcpServers": {
"directory-devrel-devrel-directory": {
"type": "http",
"url": "https://devrel.directory/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.
- 13 Sept 26 0
- Stability: 0.97 → pass security
- 12 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.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 8 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.
- 6 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.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Sept 2026 · Probed https://devrel.directory/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=devrel.directory | CN=WE1,O=Google Trust Services,C=US | 17 Aug 2026 | 15 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | de974a16ec94da0e313fa8e6624d1e |
| SANs: devrel.directory, *.devrel.directory | ||||||
| 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 insecure
Validation of devrel.directory. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| directory. | present | 59725 | 8 | Verified |
| devrel.directory. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://devrel.directory/mcp | Verified | 200 | |
| http (plaintext) | http://devrel.directory/mcp | HTTPS enforced | 308 | https://devrel.directory/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 →
directory_stats ~195
Aggregate statistics across devrel.directory in one call: listing counts by category; active job count, distinct hiring companies, the workplace mix (remote/hybrid/onsite counts), the share of roles that are remote or remote-friendly (the site's own classification, which also reads remote-prefixed locations), and salary min/median/max computed ONLY over roles stating USD pay (currencies are never blended); upcoming event count, open CFPs, and CFPs closing within 30 days. Every salary figure carries n, the number of disclosing roles - always cite n alongside any salary figure, and treat a small n as a weak signal; smallSample is true when that sample is below the threshold the site itself requires before quoting a headline salary, so qualify the figures rather than repeating them flat. Each section carries a canonicalUrl to the devrel.directory page behind it, and methodologyUrl links the page stating how the salary figures are computed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_listing ~142
Get the full detail for one directory listing by its slug, including longer details when present, the source repository URL and its maintenance signals where the listing has one (bucketed star count, last commit and last release month, whether GitHub reports the repository archived, and the date all of those were checked), the slugs of similar listings, curated alternatives and complements (hand-picked substitutes and stack pairings, as slug + name), and any open DevRel jobs or upcoming events cross-linked to the same company. Returns an error for an unknown slug.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The listing slug, as returned by search_directory (e.g. 'answer-overflow'). |
No output schema declared.
No examples provided.
list_events ~120
List DevRel events and conferences with their call-for-papers deadlines. Defaults to upcoming events only; set upcomingOnly to false to include past events, or cfpOpenOnly to true to keep only events whose CFP is still open. Each result includes the external event url and a canonicalUrl to the events page on devrel.directory.
| Name | Type | Req | Description |
|---|---|---|---|
| cfpOpenOnly | boolean | – | When true, only events whose call for papers is still accepting submissions. |
| upcomingOnly | boolean | – | Default true; set false to include events that have already started or ended. |
No output schema declared.
No examples provided.
list_jobs ~239
List currently open DevRel job postings. Filter by a free-text query (matched against title, company, location, and tags), a remote flag, an employment type, a seniority level, and/or a minimum salary - the same filters, with the same semantics, as the site's jobs page. Salary fields are passed through exactly as the posting states them. Each result includes the external posting url and a canonicalUrl to the job on devrel.directory.
| Name | Type | Req | Description |
|---|---|---|---|
| employmentType | string | – | Filter to one employment type (postings that omit it are treated as full-time). |
| level | string | – | Filter to one seniority bucket, derived from the job title the way the site derives it (management titles outrank IC prefixes). |
| query | string | – | Case-insensitive substring matched against title, company, location, and tags. |
| remote | boolean | – | When true, only remote roles; when false, only non-remote roles. |
| salaryFloor | integer | – | Only roles whose stated yearly pay could reach this amount (compared against the highest stated bound, in the posting's own currency; roles with no stated pay never qualify). |
No output schema declared.
No examples provided.
search_directory ~102
Search the devrel.directory listings of DevRel tools, communities, newsletters, podcasts, and agencies. Filter by a free-text query (matched against name, description, and tags) and/or an exact category. Each result includes the external url and a canonicalUrl to the listing's page on devrel.directory.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Exact listing category to filter to. |
| query | string | – | Case-insensitive substring matched against name, description, and tags. |
No output schema declared.
No examples provided.
search_docs ~72
Search the devrel.directory unified index of documentation guides, blog posts, directory listings, jobs, and events (including which have an open call for papers). Returns matching results with absolute devrel.directory URLs; event results deep-link to the specific event on the events page.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The search query. |
No output schema declared.
No examples provided.
What is the DevRel Directory MCP server?
DevRel Directory is an MCP server listed in the public MCP registry as directory.devrel/devrel-directory. Search DevRel tools, communities, jobs, events, CFPs, and guides from devrel.directory. This page covers its hosted endpoint (https://devrel.directory/mcp).
Is the DevRel Directory MCP server safe to use?
DevRel Directory scores 81 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 DevRel Directory MCP server expose?
DevRel Directory exposes 6 tools: search_directory, get_listing, list_jobs, list_events, directory_stats, search_docs. Their descriptions and schemas cost roughly 870 tokens of context every time the server is loaded.
Does the DevRel Directory MCP server require authentication?
No. We connected to DevRel Directory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DevRel Directory MCP server still maintained?
DevRel Directory is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.