👑

MCP QUEEN

ai.finestructure/fine-structure A

Remote MCP server for agents that create, edit, validate, and publish Fine Structure apps.

AI & Agentsv1.0.0streamable-httpfinestructure.ai

Grade evidence — probed 2026-07-17 22:15 UTC

CriterionPointsObserved
reachability25 / 25HTTP 200, initialize accepted in 391ms
protocol15 / 15valid JSON-RPC initialize result, protocolVersion 2024-11-05, serverInfo fine-structure-mcp@1.0.0
tooling35 / 35tools/list OK: 92 tools e.g. "create_app"; 92/92 described, 92/92 fully-typed schemas, median description 107 chars
latency10 / 10initialize round-trip 391ms
provenance12 / 15description present; no repository URL; version 1.0.0; namespace ai.finestructure matches endpoint/repo

Score 97/100 · latency 391ms · 92 tools · protocol access: open

Trust receipt

Security, data integrity, citation quality, and advertised claims are measured separately from protocol uptime. Missing evidence is marked unverified, never converted into a pass.

DimensionMetricStatusEvidenceSource
citation_qualitycitation_capability_advertisedunverifiedMetadata/tool descriptions advertise citation or evidence capability: validate_entity_relationships Validate entity relationship metadata and *_id references against existing entity schemas. No response-level citation benchmark has verified this claim yet.live_probe
securitysensitive_capabilities_declaredconcern10 discovered tool(s) advertise potentially state-changing or privileged capabilities. Tool names: read_app_file, read_app_files, write_app_file, rename_app_file, add_file_change, list_secret_keys, set_secret, delete_secret, configure_integration, delete_ab_test. Classification is description-based and does not prove exploitability.
Observed value: read_app_file, read_app_files, write_app_file, rename_app_file, add_file_change, list_secret_keys, set_secret, delete_secret, configure_integration, delete_ab_test
Sample: n=10
live_probe
securityauthentication_boundaryobservedLive protocol probe observed auth_state=open. This describes discovery/access behavior; it is not by itself a vulnerability finding.
Observed value: open
live_probe

Machine-readable receipt: /api/trust/ai.finestructure/fine-structure.json

Connect your agent

Claude Code:

claude mcp add --transport http fine-structure https://finestructure.ai/api/mcp

Generic MCP client config:

{ "mcpServers": { "fine-structure": { "type": "http", "url": "https://finestructure.ai/api/mcp" } } }

MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point. Share this server: permalink https://mcpqueen.com/s/ai.finestructure/fine-structure · referral link https://mcpqueen.com/go/ai.finestructure/fine-structure (counts as “routed via the queen”).

Own this server? Embed your grade badge

Live operational-grade badge, re-probed continuously — not a security or data-quality certification. Put it in your README and link to the complete receipt:

MCP Queen grade badge for ai.finestructure/fine-structure

[![MCP Queen grade](https://mcpqueen.com/badge/ai.finestructure/fine-structure.svg)](https://mcpqueen.com/s/ai.finestructure/fine-structure)

Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.

Queen Watch

Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.

Probe history

When (UTC)GradeScoreLatency
2026-07-17 22:15A97391ms

← Back to the evidence registry