Apitier MCP Server vs MCP Server Health Mon… | AllMCPs
Side-by-Side Model Context Protocol Comparison
Apitier MCP Server vs MCP Server Health Monitor
In-depth architectural comparison of the Apitier MCP Server and MCP Server Health Monitor MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Apitier MCP Server
Developer Tools · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
MCP Server Health Monitor
Developer Tools · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Apitier MCP Server if you need specialized Developer Tools tools running via a local process. Choose MCP Server Health Monitor if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Apitier MCP Server when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Full UK business onboarding check in one call.** Validates VAT, verifies Companies House, retrieves PSC (beneficial owners), and confirms the registered address. Returns `PASS / REVIEW / FAIL`, a risk score, and the full data bundle. Requires `postcode` + `vat` + `leadAgent` subscriptions.
verify_uk_address
Verify a UK address against Royal Mail PAF — returns canonical address, UPRN, UDPRN, and per-delivery-point geocode
lookup_uprn
Look up a full AddressBase record by UDPRN — returns UPRN, PAF canonical address, coordinates. Use UDPRN from `verify_uk_address
lookup_uk_postcode
UK postcode → full PAF address list + district, ward, county, country, and geocode
verify_uk_company
Look up a UK company on Companies House by name or number — status, address, SIC codes, filing health
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Apitier MCP Server is categorized under Developer Tools and uses a local stdio subprocess. In contrast, MCP Server Health Monitor belongs to Developer Tools using local stdio subprocess. Select Apitier MCP Server when you need capabilities focused on developer tools and MCP Server Health Monitor when you require tools for developer tools.
Persons with Significant Control register for a UK company — required for AML beneficial ownership checks
validate_sort_code
Validate a UK sort code and optionally a bank account number (Vocalink modulus check). No API key required.
validate_vat
Validate UK and EU VAT numbers — checks HMRC for GB numbers, EU VIES for all other country prefixes. Returns registered business name and address. Accepts any country prefix (e.g. `GB123456789`, `DE123456789`, `FR12345678901`).
validate_email
Validate email — syntax, MX, SMTP reachability, disposable domain check. Works for any email address globally.
validate_phone
Validate and parse phone numbers — accepts any international format, returns country, carrier, and line type.
lookup_india_pincode
Indian PIN code → state / district / town
generate_barcode
Generate barcode image (Code128, EAN-13, UPC, and more)
+2 more tools listed on main page
MCP Server Health Monitor Tools (8)
health_check_all
probes all configured servers in parallel via `list_tools`, measures latency, and stores results. Accepts an optional `timeout_ms` parameter (default: 5000).
get_server_status
returns per-server detail including latency, last seen time, 24-hour error count, last error message, and p50/p95 latency percentiles. Requires `server_name`.
list_degraded
filters to servers that are offline or have latency above the threshold. Accepts an optional `latency_threshold` override.
get_history
returns raw health check history for a specific server, ordered most-recent first. Requires `server_name`; accepts optional `limit` (default: 50, max: 500).
configure_server
registers a new MCP server to monitor. Servers added this way are stored in `~/.mcp/extra-servers.json` and merged with auto-discovered servers. Required: `name`, `command`. Optional: `args`, `env`.
remove_server
removes a manually registered server from monitoring. Only affects servers added via `configure_server`; auto-discovered servers are not affected. Requires `name`.
check_updates
detects version drift by hashing tool schemas on each probe and comparing against the last stored hash. Returns `has_changed`, `previous_hash`, `current_hash`, and `changed_at` per server.
export_dashboard
generates a self-contained single-file HTML dashboard with summary cards, per-server status table with p50/p95 latency, and inline SVG uptime sparklines. Accepts an optional `output_path` to write to disk.