Licensed, rights-cleared content for AI agents - verifiable license keys + EU AI Act attestation.
Most developer tooling work still happens through a UI a human drives. Opedd MCP server moves it into the conversation instead. Licensed, rights-cleared content for AI agents - verifiable license keys + EU AI Act attestation.
Licensed, rights-cleared content for AI agents — the alternative to unlicensed scraping for RAG, AI search, and LLM grounding.
The server publishes 4 tools. What each one is for:
Rights — Verifiable license key per article, publisher-authorizedProof — On-chain (Tempo blockchain) — independently verifiablePricing — Publisher sets their own price per articleProtocol — REST + MCP nativeConfiguration is passed through the environment: OPEDD_BUYER_EMAIL, OPEDD_PAYMENT_METHOD_ID, OPEDD_KEY, OPEDD_BUYER_TOKEN, OPEDD_ACCESS_KEY, OPEDD_API_KEY, OPEDD_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Opedd's toolset — Rights, Proof, Pricing and 1 more — is a fair guide to whether it matches your workflow. It is maintained by com.opedd; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Rights | Verifiable license key per article, publisher-authorized |
| Proof | On-chain (Tempo blockchain) — independently verifiable |
| Pricing | Publisher sets their own price per article |
| Protocol | REST + MCP native |
{
"mcpServers": {
"opedd": {
"url": "https://mcp.opedd.com/mcp",
"headers": { "Authorization": "Bearer ${env:OPEDD_KEY}" }
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| OPEDD_BUYER_EMAIL | Configuration value read at startup. | Optional |
| OPEDD_PAYMENT_METHOD_ID | Configuration value read at startup. | Optional |
| OPEDD_KEY | Credential the server authenticates with. | Yes |
| OPEDD_BUYER_TOKEN | Credential the server authenticates with. | Yes |
| OPEDD_ACCESS_KEY | Credential the server authenticates with. | Yes |
| OPEDD_API_KEY | Credential the server authenticates with. | Yes |
| OPEDD_API_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.