Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
EU AI Act and SB 942 obligations for AI systems: each date, the article setting it, signed sources
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://luiqtimzcsoqnizybifs.supabase.co/functions/v1/lunara-mcpRun this in your terminal
claude mcp add --transport http intelligence https://luiqtimzcsoqnizybifs.supabase.co/functions/v1/lunara-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"intelligence": {
"url": "https://luiqtimzcsoqnizybifs.supabase.co/functions/v1/lunara-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": {
"intelligence": {
"type": "http",
"url": "https://luiqtimzcsoqnizybifs.supabase.co/functions/v1/lunara-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://luiqtimzcsoqnizybifs.supabase.co/functions/v1/lunara-mcpMenu 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 lunarasociety.com (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.0.0) reached the registry 26 days 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, MCP Server Autocad Lisp Helper
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.
High-precision static analysis and debug server for AutoCAD AutoLISP (.lsp) files.
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.
Regulatory obligations for AI systems, with the article that sets each date and a link to primary law.
Your model very likely knows some of these dates wrong. The EU AI Act was amended on 27 July 2026 by Regulation (EU) 2026/1744, which deferred the Annex III high-risk obligations by sixteen months — five days before they would have applied — while leaving Article 50 exactly where it was. Any training corpus assembled before that carries the superseded date, and the two are quoted together often enough that getting one right is no evidence of getting the other right.
This server exists so a model can look the answer up instead of recalling it.
The hosted endpoint is live. The npm package is not published yet — the install command below resolves to nothing until the @lunara scope is claimed, and this repository refuses to advertise it in the meantime.
Point any MCP client that speaks Streamable HTTP at:
https://luiqtimzcsoqnizybifs.supabase.co/functions/v1/lunara-mcp
Once the package is published, this is the local alternative:
// Claude Code: .mcp.json — or claude_desktop_config.json
{ "mcpServers": { "lunara": { "command": "npx", "args": ["-y", "@lunara/mcp"] } } }
Node 18 or later. No dependencies, no API key, no account. Reading is free and always will be: a claim nobody can check is worth nothing.
If you cannot run a local process, the same server answers over HTTPS:
https://luiqtimzcsoqnizybifs.supabase.co/functions/v1/lunara-mcp
Streamable HTTP, one POST per JSON-RPC message, stateless, no key. Both transports import the same module, so they cannot drift into giving different dates.
Every document this server reads is published with a detached Ed25519 assertion over its SHA-256, and the server verifies it on each fetch. A corpus that fails verification produces an error, not an answer — a client that reports a bad signature and then answers anyway has told you something is wrong and acted as though it were not.
Verification being *unavailable* is different from verification *failing*, and they are reported differently: a runtime without Ed25519 in WebCrypto, or an authority serving no assertion, reads as unverified rather than being dressed up as verified. Keys are at /.well-known/keys.json, the method and a worked example at https://lunarasociety.com/signing.html.
| Tool | Answers |
|---|---|
lunara_obligations | What is in force, what is coming, what does instrument X require |
lunara_applicability | Which of these reach *this* deployment — and which do not |
lunara_cite | The citation block for one obligation, for when you are about to state a date to someone |
lunara_verify | Whether a business carries Lunara Shield certification |
lunara_integrity | Whether the corpus this server just read is genuinely ours, unaltered |
It does not answer when it cannot reach the authority. There is no bundled copy of the corpus. A cached table would let this server keep answering with a date that was amended months ago, which is exactly the failure the institution publishing it has already had to correct. If lunarasociety.com is unreachable, you get an error explaining that, not a remembered date. An oracle that guesses is worse than an oracle that is down, because you cannot tell which answer you got.
It will tell you nothing applies. Three outcomes of the applicability model conclude that no obligation in the corpus reaches the asker, including the one most people hit: the California AI Transparency Act reaches generative systems above one million monthly users, and below that line it imposes nothing. A qualifier that only ever escalates is a sales funnel.
It is not legal advice. Obligations are marked verified — checked against primary law, with that source linked so you can reach the same conclusion without trusting us. The applicability model is marked interpretation, because which obligation catches you is our reading. You are free to take the facts and leave the reading.
https://lunarasociety.com/corpus/obligations.json, generated from a single obligation table and gated in CI so the published corpus and the site can never disagree. Tense is never stored anywhere — a static document does not know when it is being read, so it states application dates, and this server computes "in force" against the moment of your call.
Corrections, including two we published against ourselves and the policy that requires it: https://lunarasociety.com/evidence.html
If an entry does not follow from the source it cites, that is a defect. — we would rather be told than found out.