MCP directory listing copy (draft for #71)¶

Draft, 2026-10-05. The status table below says which listings are live. Every fact below is copied from docs/guides/MCP_INTEGRATION.md and PRODUCT.md; if either changes, change this file.

Status of listings (Registry, Glama, Smithery and awesome-remote re-checked 2026-10-07 by looking at each site; the other rows are as of 2026-10-05; see "More directories" below)

Directory	Status
Official MCP Registry	Listed. `io.github.magiccadai/magicon` v1.0.0, active, published 2026-10-01 (registry API, searched "magicon").
Claude Connectors Directory	Submitted 2026-10-05. Review result not recorded yet: only the owner sees the portal and the reviewer mail (issue #71).
Glama	Listed and claimed (claimed 2026-10-06, DNS TXT `_glama-claim.api.pcbgenerator.com`; keep that record). The page shows "Ownership verified", Healthy, last tested 2026-10-07 13:14, TDQS score A, 4.3/5.
PulseMCP	Not listed. Submissions are paused; PulseMCP says it will pick servers up from the Official MCP Registry when it reopens. Nothing to do.
Smithery	Not listed (Smithery's registry, searched "magicon": no MagicON in the results). Not yet, by the owner's choice (2026-10-07), until the shared rate-limit risk below is tested.
awesome-remote-mcp-servers (GitHub list, also feeds remote-mcp.com)	Pull request opened 2026-10-07 from `magiccadai`: jaw9c/awesome-remote-mcp-servers#1158. Waiting for the list's owner.
mcp.so	Skipped: its form asks for a GitHub URL and our repo is private. Its page refused to load for me (HTTP 403), so the form itself is not verified.

Before you submit: the hosting guard (#68) is reported fixed and deployed in that issue's comments (PR #127, 500-session cap, IPv6-safe rate limit). I did not re-test the live site; Glama's own check reported it Healthy on 2026-10-07.

Name¶

MagicON AI

One-liner (under 100 characters)¶

RF module and PCB design engines for your AI assistant. Real catalog parts, computed numbers.

Short description (about 300 characters)¶

Design RF modules from your AI assistant. Give a frequency and an output power and get a transmit chain with real catalog parts, a priced parts list and a solved PCB stackup. Every number comes from a solver, not from the AI. No account, no API key.

Long description¶

MagicON AI designs RF modules: the radio part of a product (amplifiers, filters, mixers) and the circuit board under it. This server gives your assistant the same engines the website uses.

Ask your assistant to design a transmit chain, a superheterodyne receiver, or a shared-antenna transmit/receive front end. It picks real parts from its parts catalog, works out signal levels and noise, solves a PCB stackup against impedance targets, and checks heat, power delivery and standards limits.

The promise: every number comes from a solver. Without one, an assistant searches the web, finds a part, and can pick a different part each time you ask the same question. Here the assistant asks a solver and the solver computes it. A check_grounding tool lists any figure in a draft that no engine produced. A slot that no catalog part can fill is reported as missing, never filled with an invented part.

Every tool is read-only. There is no sign-in. The session remembers computed results, so after a design you can ask for thermal, power-delivery and compliance checks without re-sending figures.

Tools (fourteen)¶

Tool	What it does
`design_rf_chain`	Transmit chain from a frequency and output power, with real parts, a priced parts list and disclosures
`design_rf_receiver`	Superheterodyne receiver: frequency plan, noise, sensitivity, converter interface
`design_tr_module`	Shared-antenna transmit/receive front end and its safety budgets
`run_link_budget`	Cascaded gain, noise figure and headroom for stages you supply
`run_stackup_solver`	PCB stackup against impedance targets
`run_thermal_analysis`	Junction temperature and board heat
`run_pdn_analysis`	Power-delivery impedance
`run_compliance_analysis`	Standards checks on the solved stackup and the chain's output
`run_ota_link`	One-way over-the-air link: EIRP, path loss, received power, margin, maximum range
`run_radar_performance`	Radar range equation (received power, SNR, maximum detection range) and pulsed-waveform limits
`run_planar_filter`	Low-pass or band-pass filter made of copper on the PCB: sections, footprint, simulated response
`design_patch_antenna`	Rectangular microstrip patch antenna or a planar array of it: dimensions, resonance, bandwidth, gain, beamwidths
`run_glass_weave_analysis`	Which PCB glass-weave style keeps impedance variation inside the tolerance, ranked by cost
`check_grounding`	Checks a draft against the results computed in the session; computes nothing

Connect¶

Address: https://api.pcbgenerator.com/mcp/ (Streamable HTTP, no sign-in)

claude mcp add --transport http magicon https://api.pcbgenerator.com/mcp/

Example prompts¶

"Design a 5.8 GHz, 1 W transmit chain and give me the parts list."
"Design an X-band receiver and tell me its sensitivity."
"Design a 20 W X-band T/R module and check what the receiver sees while transmitting."
"Solve a stackup for 50 ohm microstrip, then check heat and power delivery."
"Check this summary against the computed results before I send it."

Honest limits (include where the form allows)¶

10 requests per minute per IP address; over that you get HTTP 429.
No CAD export over MCP (KiCad, ODB++, Gerber need a free signed-in account on the website).
Compliance results compare a design with published limits. They are not a certification.

Links¶

Website: https://pcbgenerator.com
MCP guide: docs/guides/MCP_INTEGRATION.md
How MagicON grounds its numbers: https://pcbgenerator.com/how-we-ground

Connectors Directory form (verified 2026-10-05, official page)¶

Portal: claude.ai/directory/manage → Submit new → MCP connector. Needs a paid Claude plan. Anthropic scans it automatically and by default lists it as a "Community" connector; some get a human review. Escalations: mcp-review@anthropic.com.

Step	What it asks	Answer
Connection	`https://` server URL	`https://api.pcbgenerator.com/mcp/`
Tools	Synced from the live server. Each tool needs a `title` and `readOnlyHint` or `destructiveHint`	`backend/mcp_server/tools.py:117-134` (`tool_annotations`) and `grounding_check.py:83` set both (read-only). I did not check each tool against the live server — the portal flags any that are missing.
Listing	Name ≤100 chars, one-liner ≤200, description ≤2,000, 1–5 categories, documentation URL, privacy policy URL, support contact, icon, URL slug (permanent once published)	Text above fits the limits (re-count the long description when you paste it). Docs URL and privacy URL: you choose.
Use cases	Primary use cases, what users need before connecting, reads/writes/both	Example prompts above · nothing needed · reads only
Company	Company name, website, primary contact	Yours
Authentication	OAuth, custom, or none	None (public, no sign-in)
Data handling	Own API / partner / third party; health data; sponsored content	Own engines and own catalog — confirm; no health data, no sponsored content
Test & launch	Reviewer access steps; you confirm you ran every tool	No account needed. Run all fourteen tools once as a custom connector first.
Compliance	Seven policy acknowledgments, all required	You read and tick them

Not needed for us: carousel screenshots (MCP Apps only) and allowed link URIs (optional).

Still needed from you¶

An icon, a support contact, a documentation URL, a privacy policy URL, and 1–5 categories.
A company name and website (or your own name).
Pick the URL slug carefully: it cannot change after publishing.

Paste-ready form answers (2026-10-05)¶

Open claude.ai/directory/manage → Submit new → MCP connector. Values marked YOU cannot come from the repo.

Step / field	Paste this
Connection · URL	`https://api.pcbgenerator.com/mcp/`
Listing · Name	MagicON AI
Listing · One-liner (93 chars)	RF module and PCB design engines for your AI assistant. Real catalog parts, computed numbers.
Listing · Description	the "Long description" section above (979 chars)
Listing · Categories (1–5)	YOU pick from the portal's list (I could not verify its category names). Fit: engineering / developer tools / science.
Listing · Documentation URL	YOU choose. The guide is `docs/guides/MCP_INTEGRATION.md` in the repo; the site page that serves it is not verified. `https://pcbgenerator.com/how-we-ground` exists (`App.tsx:247`).
Listing · Privacy policy URL	`https://pcbgenerator.com/privacy` (route at `App.tsx:256`; rewritten in PR #133)
Listing · Support contact	`support@pcbgenerator.com` (`frontend/src/config/emails.ts:12`; it is the address on the privacy page)
Listing · Icon	YOU
Listing · URL slug (permanent)	suggest `magicon` — YOU confirm
Use cases	Design an RF transmit chain, receiver or T/R front end from a frequency and power; solve a PCB stackup; check heat, power delivery and standards limits; check a draft for figures no solver produced.
Needed before connecting	Nothing: no account, no key.
Reads or writes	Reads only (every tool is read-only; session memory is gone when the connection ends).
Company name / website	YOU (website: `https://pcbgenerator.com`)
Primary contact	YOU
Authentication	None (public data, no sign-in)
Data handling · API	Own engines and own parts catalog (the MCP guide says the tools "read the part catalog and compute"). YOU confirm no third-party API is proxied; I did not check. Personal health data: no. Sponsored content: no.
Test & launch · reviewer access	"No account needed. Add `https://api.pcbgenerator.com/mcp/` as a custom connector. Try: 'Design a 5.8 GHz, 1 W transmit chain.' Limit is 10 requests a minute per IP address, so wait a minute after a full session."
Test & launch · confirm tools run	YOU must run all fourteen tools once as a custom connector first.
Compliance (7 acknowledgments)	YOU read and tick each one.

Not verified: the portal's exact category names and wording; that the live /mcp/ answers today.

More directories (checked 2026-10-05)¶

Order: easiest and safest first. Where they stand (2026-10-07): 1 is done, 2 is sent and waiting, 3 is on hold by the owner's choice. The steps below are kept as they were written.

1. Glama: claim the listing that already exists¶

Done 2026-10-06: claimed by the owner through the domain (DNS TXT _glama-claim.api.pcbgenerator.com; keep that record). The page shows "Ownership verified" (2026-10-07).

Page: https://glama.ai/mcp/connectors/io.github.magiccadai/magicon (healthy, 9 tools, last tested 2026-10-06 02:54, unclaimed).
Glama's own wording: the author "can claim ownership by verifying the domain or GitHub account it belongs to". Claiming gives you its health checks and usage figures and lets you edit the listing.
Steps: open the page → Claim ownership → sign in to Glama → verify the GitHub account magiccadai (it matches the io.github.magiccadai name) or the domain pcbgenerator.com.
Not verified: the exact verification steps after you sign in.

2. awesome-remote-mcp-servers: one pull request¶

Sent 2026-10-07: jaw9c/awesome-remote-mcp-servers#1158, opened from magiccadai by a Claude session on the owner's yes, with the row, title and description below unchanged (one line added to README.md, after the Wolfram row).

A GitHub list of hosted MCP servers (1,130 stars, last updated 2026-09-24). remote-mcp.com shows the same list and says to add servers there.

Row to add (header is Name | Category | URL | Authentication | Maintainer):

| MagicON AI | Engineering | `https://api.pcbgenerator.com/mcp/` | Open | [MagicON AI](https://pcbgenerator.com) |

⚠ Their rules say "OAuth 2.0 or API Key support required", yet 29 rows in the list say Open (for example AWS Knowledge). So they may still turn us down. No "Engineering" category exists yet; "Scientific Research" is the nearest one already used. Keep "Engineering", or pick that one.
They prefer servers run by the company behind them; ours is.
⚠ Expect a slow answer, or none: on 2026-10-06 the repo had at least 200 open pull requests (GitHub search counted 645 on 2026-10-07), and the newest merged one was from 2026-06-23. A no-sign-in server has got in before (Wolfram, merged June 2026).

Paste-ready pull request (2026-10-06). On GitHub: open the repo → README.md → the pencil (Edit) → GitHub makes a fork for you. Add the row below as the LAST row of the "Remote MCP Server List" table (new rows go at the bottom; the table is not in A–Z order) → "Propose changes" → "Create pull request". Their CONTRIBUTING.md asks the description to say why the server meets their quality criteria, how it is used in production, and its notable features.

Row (category "Engineering" is new; their rules also allow "Other"):

| MagicON AI | Engineering | `https://api.pcbgenerator.com/mcp/` | Open | [MagicON AI](https://pcbgenerator.com) |

Title: Add MagicON AI (RF and PCB design engines)

Description:

Adds MagicON AI, the official remote MCP server of pcbgenerator.com, run by the company behind it.

What it does: RF module and PCB design engines for an assistant: transmit chains, receivers and
transmit/receive front ends built from a catalog of real parts, plus PCB stackup solving against
impedance targets, heat, power-delivery and standards checks. Every number comes from a solver,
not from the model; a check_grounding tool lists any figure in a draft that no engine produced.

Quality criteria
- Official: run by MagicON AI on its own domain; the same engines serve the pcbgenerator.com web app.
- Listed in the Official MCP Registry as io.github.magiccadai/magicon.
- Security: all fourteen tools are read-only; no sign-in and no user data needed. A per-address rate
  limit (10 requests a minute) and a cap on open sessions protect the service.
- Support: support@pcbgenerator.com. Privacy policy: https://pcbgenerator.com/privacy

Authentication is "Open", like other entries in the list (for example Wolfram), because the tools
only compute from public catalog data.

Connect: claude mcp add --transport http magicon https://api.pcbgenerator.com/mcp/

Before you send it: the session cap is MAX_MCP_SESSIONS = 500 in backend/mcp_server/http.py:89 and the 10-a-minute limit is in backend/mcp_server/README.md:15; neither was re-tested on the live site for this draft. Leave out anything you are not happy to state in public.

3. Smithery: publish by URL (decide on the risk first)¶

On hold (owner's choice, 2026-10-07): not yet, until the shared rate-limit risk below is tested.

How: go to https://smithery.ai/new, enter https://api.pcbgenerator.com/mcp/, and finish the steps. The command-line version is smithery mcp publish "https://api.pcbgenerator.com/mcp/" -n @<your-org>/magicon. Smithery reads the tool list from the live server itself.
Account and cost: Smithery's docs don't say. Not verified.
⚠ Risk, not measured: Smithery's docs say its "Gateway proxies to your upstream server", and its requests "originate from Cloudflare Workers". Our limit is 10 requests a minute per address for anyone without a sign-in (backend/mcp_server/ratelimit.py, caller_key). If users reach us through Smithery, many of them may share a few addresses and so share one 10-a-minute allowance. That would show up as HTTP 429 errors for people who did nothing wrong. Whether the addresses are really shared has not been tested.

Skipped¶

PulseMCP: submissions paused. It says the Official MCP Registry is "the best first step" and it will pick servers up from there. We are already in that registry.
mcp.so: its form asks for a GitHub URL; our repo is private.

Sources: registry.modelcontextprotocol.io (/v0/servers?search=magicon), glama.ai connector page, pulsemcp.com/submit, github.com/jaw9c/awesome-remote-mcp-servers README, smithery.ai/docs/build/publish, registry.smithery.ai (/servers?q=magicon).