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.

Opedd — Licensed Content for AI

NPM · OPEDD-MCP · 2 COMPONENTS · SCANNED SEP 22

Licensed, rights-cleared content for AI agents - verifiable license keys + EU AI Act attestation.

0 this week 80 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 34 of 109 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1968 tokens (~246/item across 8 items; 8 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 Management88
  • Stability check failed: the tool surface changed between 0.6.8 and 0.6.15: 0 tool removals, 2 breaking changes, 0 additions. See how to fix → Fail
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
Install

How do I install the Opedd — Licensed Content for AI MCP server?

Opedd — Licensed Content for AI runs locally as an npm package, launched with npx -y opedd-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · opedd-mcp

# add to Claude Code
claude mcp add com-opedd-opedd-mcp -- npx -y opedd-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "com-opedd-opedd-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "opedd-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-opedd-opedd-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "opedd-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-opedd-opedd-mcp -- npx -y opedd-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-opedd-opedd-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "opedd-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-opedd-opedd-mcp --command npx --arg -y --arg opedd-mcp
# ~/.hermes/config.yaml
mcp_servers:
  com-opedd-opedd-mcp:
    command: "npx"
    args: ["-y", "opedd-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-opedd-opedd-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "opedd-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-opedd-opedd-mcp -t stdio -c npx -a -y opedd-mcp
// mcp.json
{
  "mcpServers": {
    "com-opedd-opedd-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "opedd-mcp"
      ]
    }
  }
}
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.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 81 to 84.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 74 to 78.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 68 to 71.

  • 16 Sept 26 −3

    No change was recorded against any check on this day. Stability & Change Management went from 88 to 68.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 81 to 84.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 74 to 78.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 68 to 71.

  • 9 Sept 26 −3

    No change was recorded against any check on this day. Stability & Change Management went from 88 to 68.

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 22 Sept 2026 · Analysed npm/opedd-mcp@0.6.15

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 109 packages
Packages resolved 109
Stale 34
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~1,740 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
browse_registry ~107

Browse the public Opedd license registry. Returns recently issued licenses and licensable content. Filter by publisher_id to explore all content from a specific publisher. Filter by article_id to see all licenses issued for a specific article.

NameTypeReqDescription
article_idstringFilter results to a specific article (UUID)
limitnumberNumber of results to return (default: 10, max: 50)
publisher_idstringFilter results to a specific publisher (UUID)

No output schema declared.

No examples provided.

detect_platform ~203

Detect the content platform behind a URL via POST /detect-platform (Phase 12 Wave 3 W3.1). Public no-auth lookup. Given a URL, identifies what platform powers it (Substack / Beehiiv / Ghost / Medium / Brevo / custom) and returns the suggested onboarding workflow. Hostname-detectable platforms (Substack subdomain, Beehiiv suffix, etc.) resolve in milliseconds; custom domains may take ~few seconds while the detector probes well-known platform endpoints in parallel. Returns: {platform, confidence, archive_method, forward_method, required_credentials, instructions}. The archive_method + forward_method fields are the two onboarding-workflow inputs Opedd's setup wizard reads (one for historical content backfill, one for new-content forward stream). instructions is human-readable operator copy explaining the inferred path.

NameTypeReqDescription
urlstringyesPublisher URL to inspect (any well-formed URL works; hostname-match short-circuits the probe path).

No output schema declared.

No examples provided.

lookup_content ~82

Look up a piece of content on the Opedd registry by URL. Returns the article title, publisher, available license types, and pricing (human republication price and AI training/inference price). Always call this first to check if content is licensable and what it costs.

NameTypeReqDescription
urlstringyesThe canonical URL of the article or content to look up

No output schema declared.

No examples provided.

publisher_directory ~209

Browse the public Opedd publisher catalog via GET /publisher-directory. Returns paginated publishers with article counts, pricing (per-article + annual + monthly-forward-feed), plan, and sample articles (RAG-extended metadata). **The primary discovery surface for AI labs to find Opedd-licensable publishers** — distinct from `browse_registry` (which lists issued LICENSES, not publishers). Filter by category (case-insensitive substring), min_articles, or verified status. Public no-auth — useful pre-purchase scoping before buyers commit to enterprise-license POST.

NameTypeReqDescription
categorystringCase-insensitive substring filter on publisher category (e.g. 'finance', 'AI').
limitnumberPage size cap.
min_articlesnumberFilter to publishers with at least this many licensable articles.
offsetnumberPagination offset.
verifiedstring'true' to show only verified publishers (default), 'false' for unverified.

No output schema declared.

No examples provided.

purchase_enterprise_license ~409

Purchase a bulk enterprise license covering multiple publishers (Phase 10). Returns a Stripe client_secret for payment completion + the enterprise_license_id. After payment, an ent_* access key is emailed to buyer_email. Scopes: 'custom' (pass-through publisher_ids), 'platform_wide' (auto-resolve all opted-in publishers), 'filtered' (Phase 10 filter_rules). License tiers: 'rag' (= ai_retrieval), 'training' (= ai_training, flat-fee not metered), 'inference' (= ai_retrieval), 'full_ai' (writes both retrieval + training records). The buyer must accept the Opedd Master Services Agreement (opedd.com/terms) before purchase — set terms_accepted=true to record it.

NameTypeReqDescription
billing_typestringBilling cadence (default: annual)
buyer_emailstringyesEmail to deliver the access key after payment
buyer_orgstringyesBuyer organization name (for billing + audit ledger)
buyer_webhook_urlstringOptional HMAC-signed webhook for content.published events on covered publishers
duration_monthsnumberLicense duration in months (default: 12)
filter_rulesobjectRequired when scope='filtered'. See Phase 10 docs for shape: excluded_publisher_ids / direct_license_carveouts / categories / max_price_per_event.
license_tierstringLicense tier (default: rag)
publisher_idsarrayyesArray of publisher UUIDs. Required for scope='custom'; ignored for platform_wide/filtered (resolved server-side).
scopestringCoverage scope (default: custom)
terms_acceptedbooleanyesREQUIRED. Set true only after the buyer (your principal) has accepted the Opedd Master Services Agreement at opedd.com/terms. The current MSA version label is recorded with the licence; purchases wit…

No output schema declared.

No examples provided.

purchase_license ~329

Purchase a content license from the Opedd protocol using a Stripe payment method. Returns a license key (format: OP-XXXX-XXXX) and a certificate URL. The buyer receives a Handshake Email with their license key. Set OPEDD_BUYER_EMAIL and OPEDD_PAYMENT_METHOD_ID env vars to avoid passing them on every call. License types: 'human' = republication rights, 'ai' = training dataset rights, 'ai_inference' = inference/RAG rights.

NameTypeReqDescription
article_idstringOpedd article UUID (use this OR article_url)
article_urlstringURL of the article to license (use this OR article_id)
buyer_emailstringEmail address for the license. Falls back to OPEDD_BUYER_EMAIL env var.
buyer_namestringFull name of the buyer (for the license record and certificate)
buyer_organizationstringOrganization or company name (for enterprise/editorial licenses)
intended_usestringIntended use of the licensed content
license_typestringyeshuman = republication/editorial rights, ai = training dataset rights, ai_inference = inference/RAG rights
payment_method_idstringStripe payment method ID (pm_...). Falls back to OPEDD_PAYMENT_METHOD_ID env var.
terms_acceptedbooleanyesREQUIRED. Set true only after the buyer (your principal) has accepted the Opedd licence terms at opedd.com/terms. The acceptance timestamp is recorded with the licence; purchases without genuine acce…

No output schema declared.

No examples provided.

rsl_get ~322

Fetch a publisher's RSL Standard manifest via GET /rsl-manifest (Phase 12 Wave 1 W1.1). Public no-auth endpoint — discovery surface for AI agents/crawlers wanting to know what's licensable from a publisher BEFORE going through the buyer-account signup flow. Returns the 4 canonical license types (ai_retrieval, ai_training, human_per_article, human_full_archive) the publisher has opted into, plus the EU CDSM Article 4(3) opt-out posture (`tdm_reservation`). Set `jsonld: true` to request the JSON-LD shape with embedded HMAC-SHA256 signed receipt over the CDSM Article 4(3) reservation state + `tdm:reservationSignedAt` timestamp — regulators can post-hoc verify the reservation was the claimed value at the claimed time. Default `jsonld: false` returns the raw RSL Standard JSON manifest. Per INVARIANTS.md W1.6: this is the PUBLISHER-side CDSM Article 4(3) declaration surface. It is NOT an EU AI Act Article 53 attestation (which is buyer-side, JWT-auth, via article_53_attestation tool).

NameTypeReqDescription
jsonldbooleanIf true, request JSON-LD shape (Accept: application/ld+json) with embedded HMAC-SHA256 signed receipt. Default false returns raw RSL Standard JSON shape.
publisher_idstringyesUUID of the publisher whose RSL manifest to fetch. Publisher must be verified.

No output schema declared.

No examples provided.

verify_license ~79

Verify the authenticity of an Opedd license key. Returns license details including: article title, publisher, license type, issue date, amount paid, buyer info, and blockchain proof status. Use this to confirm a license is valid before using licensed content.

NameTypeReqDescription
license_keystringyesThe license key to verify (format: OP-XXXX-XXXX)

No output schema declared.

No examples provided.

Common questions

What is the Opedd — Licensed Content for AI MCP server?

Opedd — Licensed Content for AI is an MCP server listed in the public MCP registry as com.opedd/opedd-mcp. Licensed, rights-cleared content for AI agents - verifiable license keys + EU AI Act attestation. This page covers its npm package (opedd-mcp).

Is the Opedd — Licensed Content for AI MCP server safe to use?

Opedd — Licensed Content for AI scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. 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 Opedd — Licensed Content for AI MCP server expose?

Opedd — Licensed Content for AI exposes 8 tools: lookup_content, purchase_license, verify_license, browse_registry, publisher_directory, and 3 more. Their descriptions and schemas cost roughly 1,740 tokens of context every time the server is loaded.

Is the Opedd — Licensed Content for AI MCP server still maintained?

Opedd — Licensed Content for AI 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.

What licence is the Opedd — Licensed Content for AI MCP server under?

Opedd — Licensed Content for AI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.