Fcc Regulations vs Kentucky Code
A side-by-side look at the Fcc Regulations and Kentucky Code MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
K
Kentucky CodeLegal · Local subprocess (stdio)Kentucky Revised Statutes (KRS) — state statutes by citation and by topic.41FairAuth: no auth requiredVerdict: choose Fcc Regulations for legal work as a local process; choose Kentucky Code for legal as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Fcc Regulations when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- You want tools like
fcc_regulation, fcc_regulations_search.
KChoose Kentucky Code when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | K Kentucky Code | |
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 53/100 · Good | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner |
Tools & capabilities
Fcc Regulations tools 2
fcc_regulationGet the full text of one FCC regulation — a US Federal Communications Commission rule codified in 47 CFR — by its citation. Returns the exact regulatory wording currently in force. Answers "what does 47 CFR 15 require", "what is the FCC rule for X", "does the FCC allow X", "read 47 CFR 15.247", "th…fcc_regulations_searchKeyword search across the FCC regulations — US telecommunications rules in 47 CFR. Answers "what FCC regulations cover X", "the FCC rule about X", "find the telecommunications regulation for X", "which radio / spectrum / wireless rule applies to X". Great for topics: unlicensed device emission limi…
Kentucky Code tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Fcc Regulations
{
"mcpServers": {
"fcc-regulations": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-fcc-regulations"
]
}
}
}
Kentucky Code
{
"mcpServers": {
"kentucky-code": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-kentucky-code"
]
}
}
}
Frequently asked questions
Fcc Regulations is categorized under Legal and uses a local stdio subprocess. Kentucky Code belongs to Legal and uses a local stdio subprocess. Pick Fcc Regulations for legal work and Kentucky Code for legal.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Fcc Regulations has no declared pricing — check the project's own site. Kentucky Code is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add fcc-regulations and kentucky-code as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Fcc Regulations has a quality signal of 53/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Kentucky Code has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.