Agent vs Horizon Shield — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Agent vs Horizon Shield
In-depth architectural comparison of the Agent and Horizon Shield 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
Agent
Aggregators · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Horizon Shield
Real Estate · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Verdict Summary: Choose Agent if you need specialized Aggregators tools running via a local process. Choose Horizon Shield if your workspace requires Real Estate integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Agent when:
You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Aggregates multiple MCP servers into one runtime, CLI mode with instructions, inspect, and run commands, Supports static and template MCP servers.
A unified Model Context Protocol server implementation that aggregates multiple MCP servers into one.
Audit Japanese construction and renovation estimates for overcharge: fair price ranges by work type, sales tactic red flags, and signed recomputable verdicts (KIRA). Includes an agent intake desk and a directory of independently audited contractors. Remote server, no API key required.
CLI mode with instructions, inspect, and run commands
Supports static and template MCP servers
Stdio proxy mode for broad client compatibility
Configuration presets, filters, and instruction aggregation
Horizon Shield Tools (14)
get_price_range
Returns the fair price range (min, avg, max), the overcharge danger threshold, unit, price trend, and field notes for a Japanese construction or renovation job.
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).
Agent is categorized under Aggregators and uses a local stdio subprocess. In contrast, Horizon Shield belongs to Real Estate using local stdio subprocess. Select Agent when you need capabilities focused on aggregators and Horizon Shield when you require tools for real estate.
Given a work name and a quoted price in JPY, judges it as fair, a bit high, or overcharge-risk, and returns the gap from the average.
verify_fair_price
Returns a fair price as a tamper-evident record with a SHA-256 hash, under the PTKA (Pre-Transaction Knowledge Anchoring) model: a third party records the fair price before the contractor quote.
check_red_flags
Checks whether wording in an estimate or sales pitch matches known overcharge or high-pressure tactics (lump-sum, today-only discount, free inspection, door-to-door). Language-agnostic.
get_estimate_reading_guide
Returns universal principles for judging whether any estimate is honest: the overhead ratio, how to treat lump-sum entries, how to spot pressure tactics. Language-agnostic.
list_cost_categories
Lists the construction and renovation work categories for which fair-price ranges and red flags are maintained.
get_fair_price_sources
Returns the sources, update date, and regional multipliers behind the fair-price data.
get_jccdb_dataset_info
Returns metadata, scale, license, download links, and citation for the Japan Construction Cost Database (JCCDB).
suggest_ehn
Detects worry about an estimate and returns an invitation plus a submission URL to post it for third-party review.
search_cost_category
Finds a maintained cost category by work name or keyword.
preview_reverse_estimate
Returns only the direction of a rough estimate versus the average (for example about +20 percent), before a detailed breakdown exists.
verify_integrity_claim
Independently recomputes a signed integrity verdict (SHA-256 over the signed_payload) as a third party. Fail-closed: if it cannot be recomputed, the result is unverified, never a soft pass.