Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
OracleNet Deal Discovery Protocol — permissioned commercial matching for MCP/A2A agents.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://tooloracle.io/deal/mcp/Run this in your terminal
claude mcp add --transport http dealoracle https://tooloracle.io/deal/mcp/Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"dealoracle": {
"url": "https://tooloracle.io/deal/mcp/"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"dealoracle": {
"type": "http",
"url": "https://tooloracle.io/deal/mcp/"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://tooloracle.io/deal/mcp/Menu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain tooloracle.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.1.0) reached the registry 7 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Microsoft Exchange Online MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Exchange Online admin for MSPs: forwarding audits, EWS posture and offboarding, no PowerShell
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Status: Draft v1.1 — published for public review.
Specification and reference artefacts for a permissioned commercial matching layer for autonomous agents. This protocol defines how two software agents can:
It is explicitly not a cold-outreach channel, not a general A2A messaging protocol, and not a directory. See SPEC.md §1.5 "Scope: What This Protocol Is *Not*".
.
├── SPEC.md # The normative specification (= RFC-0001 v1.1-draft) ├── CHANGELOG.md # Version history ├── CONTRIBUTING.md # How to propose changes ├── CODE_OF_CONDUCT.md # Standard conduct rules ├── LICENSE # CC BY 4.0 (specification text) ├── schemas/ # JSON Schemas (normative) │ ├── deal-policy.v1.json │ ├── deal-proposal-card.v1.json │ ├── deal-vc-v1.jsonld │ └── deal-emergence.v1.json ├── examples/ # Minimal conformant artefacts │ ├── minimal-deal-policy.json │ ├── minimal-do-not-contact.json │ ├── minimal-deal-feed.atom │ ├── proposal-card.json │ └── deal-emergence.json ├── registry/ # Draft registry submission material │ ├── README.md # Submission policy │ ├── protocol-descriptor.json # Machine-readable pointer │ ├── a2a-registry-entry.md # Draft for A2A-style registries │ └── mcp-registry-note.md # Draft for MCP-server registries ├── docs/ # Rendered HTML + markdown copy │ ├── index.html │ ├── rfc-0001.html │ └── rfc-0001.md └── reference/ # Pointer to the live reference deployment └── README.md
A conformant implementation MUST:
deal-policy.json at /.well-known/deal-policy.json.inbox.accepts as a refusal to receive proposals.do-not-contact.json (own-side and outgoing).SPEC.md §10.3 before every outbound proposal, and log every decision in an append-only audit retained ≥ 12 months.Additional RECOMMENDED layers: Atom broadcast (deal-feed.atom), W3C VC wire format for proposals, deal-emergence.json for observed demand, HTTP Link headers for discovery.
A live reference implementation is running at:
https://feedoracle.io/.well-known/deal-policy.jsonhttps://tooloracle.io/.well-known/deal-policy.jsonWith auxiliary layers at:
https://tooloracle.io/.well-known/do-not-contact.jsonhttps://tooloracle.io/.well-known/deal-feed.atomhttps://tooloracle.io/.well-known/deal-emergence.jsonhttps://tooloracle.io/deal/intelligence?limit=20https://tooloracle.io/deal/public-stats.jsonThe full, hosted specification is at https://tooloracle.io/docs/deal-protocol/rfc-0001.
reference/README.md.registry/ folder contains *draft submission material* for external registries. Nothing in this repo has been submitted anywhere.Inbound proposals (on a conformant deal-policy basis) may be delivered to any participating inbox listed in reference/README.md. General protocol discussion: via GitHub issues on this repository once it is published, or by email to the addresses listed on the reference origins.
Specification text: CC BY 4.0. See LICENSE.