Tx Medical Exclusions vs Apier MCP
A side-by-side look at the Tx Medical Exclusions and Apier MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Tx Medical Exclusions for legal work as a local process; choose Apier MCP 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 Tx Medical Exclusions when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Apier MCP when
- You need dedicated capabilities in the Legal domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
APIER_API_KEY. - You want tools like
get_company_summary, get_public_obligations, get_exchange_rate.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Legal | Legal |
| Quality signal | 41/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | APIER_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 25 |
| Full listing | View Tx Medical Exclusions | View Apier MCP |
Tools & capabilities
Tx Medical Exclusions tools
No tool names declared yet. Check the project README from the listing page.
Apier MCP tools 25
get_company_summaryA one-shot summary of obligations and deadlines for a Norwegian organisation: your FIRST call when you orient against a company.get_public_obligationsKeyless. Retrieve the universal obligation set for a Norwegian entity type — every regulatory obligation that applies by virtue of BEING that organisational form, before per-company Tier-2 data is layered on.get_exchange_rateKeyless. Norges Bank reference exchange rate for a currency against NOK — the benchmark Norwegian tax and accounting rules accept for foreign-currency obligations.list_acting_capacityResolve every Norwegian regulatory action a person is currently authorised to perform on behalf of a specific organisation.get_company_profileResolve a Norwegian organisasjonsnummer (9 digits) into a structured company profile from Brønnøysund Enhetsregisteret: display name, form of organisation, NACE codes with descriptions, addresses, the dates of registration and dissolution, the `active` / `dissolved` status enum, the MVA-registered…check_authorizationReturn the authorisation snapshot for the calling consumer's delegation on a Norwegian organisation: the `status` enum (`full` / `partial` / `none`), `active_scopes`, `missing_scopes` (empty on `full`) and `delegated_rights`.get_company_contextBrønnøysund identity slice for a Norwegian organisation: legal name, form of organisation, NACE codes, addresses, the dates it was formed or dissolved, and the signaturrett / prokura role-code summary (never personal identifiers).get_company_deadlinesThe upcoming filing calendar for one organisation, horizon_months ahead.get_company_obligationsEvaluate the Apier Rulebook for a Norwegian organisation: one entry per rule with rule_id, obligation_name, evaluation_result (applicable, not_applicable or insufficient_data), a reason, the legal_reference, frequency, data_tier_required and the bokmål description, which is inherited byte for byte…get_public_deadlinesKeyless. The universal Norwegian filing calendar: the deadlines for every Norwegian business in the covered categories (MVA, A-melding, Skattemelding, Årsregnskap), which do not depend on any one organisation.validate_actionDry-run a proposed regulatory action with NO upstream side effect (no government call).explain_compliance_errorKeyless. Resolve a structured Apier compliance error code into a Norwegian-bokmål Explanation envelope: summary, bokmål why, ordered fix_steps, optional documentation link + legal_basis, and an optional handover block (who / where / what / why) for errors a human must resolve.- +13 more on 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.
Tx Medical Exclusions
{
"mcpServers": {
"tx-medical-exclusions": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-tx-medical-exclusions"
]
}
}
}
Apier MCP
{
"mcpServers": {
"mcp-375": {
"command": "npx",
"args": [
"-y",
"stdio"
],
"env": {
"APIER_API_KEY": "YOUR_APIER_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Tx Medical Exclusions is categorized under Legal and uses a local stdio subprocess. Apier MCP belongs to Legal and uses a local stdio subprocess. Pick Tx Medical Exclusions for legal work and Apier MCP 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.
Tx Medical Exclusions is listed as free. Auth: no auth required. Apier MCP has no declared pricing — check the project's own site. 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 tx-medical-exclusions and mcp-375 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Tx Medical Exclusions has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Apier MCP has 57/100 (Good) with 2 views, 0 installs and 0 GitHub stars.