Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DevRel Directory

REMOTE · DEVREL.DIRECTORY

Search DevRel tools, communities, jobs, events, CFPs, and guides from devrel.directory.

Available components

0 this week 33 Trust /100

Last scanned (13 hours ago)

Scores higher than 16% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Education and Research

Trust breakdown (7 categories)

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 Security83
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 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. Claim this server and supply a read-only token to verify it and lift the score.

What we tested

Checks we ran (5)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 12 Oct 26 0
    • Endpoint reachability: reachable → behind authorisation ▼ security
    • Authorization: unverified → fail ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → unverified ▼ security
    • HSTS header: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 13 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 15 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 14 Aug 26 0
    • Transport: fail → pass ▲ security
    • Authorization: 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. security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
Diagnostics

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 21 Nov 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 15 Oct 2026 13 Jan 2027 ECDSA 256 ECDSA-SHA256 7f3b2815dc2cf5c30e94613407c38fcb
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. DS published 5701 8 Verified
devrel.directory. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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 403

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://devrel.directory/mcp Auth required 403
http (plaintext) http://devrel.directory/mcp HTTPS enforced 308 https://devrel.directory/mcp
MCP tools · 6 exposed · ~870 tokens

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 →

Tool Tokens
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.

NameTypeReqDescription
slugstringyesThe 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.

NameTypeReqDescription
cfpOpenOnlyboolean–When true, only events whose call for papers is still accepting submissions.
upcomingOnlyboolean–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.

NameTypeReqDescription
employmentTypestring–Filter to one employment type (postings that omit it are treated as full-time).
levelstring–Filter to one seniority bucket, derived from the job title the way the site derives it (management titles outrank IC prefixes).
querystring–Case-insensitive substring matched against title, company, location, and tags.
remoteboolean–When true, only remote roles; when false, only non-remote roles.
salaryFloorinteger–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.

NameTypeReqDescription
categorystring–Exact listing category to filter to.
querystring–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.

NameTypeReqDescription
querystringyesThe search query.

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http directory-devrel-devrel-directory 'https://devrel.directory/mcp'
Common questions

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 33 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?

Yes. DevRel Directory 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 DevRel Directory MCP server still maintained?

DevRel Directory is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the DevRel Directory MCP server?

VerifyMCP ran 5 checks on DevRel Directory, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about DevRel Directory: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.