agent · model context protocol (mcp)

Phronesis

phronesisintel.comevidence retrieved Aug 1, 2026view as JSON all model context protocol (mcp) entries 4 alternatives

Indexed12 or more fields evidenced; not yet scored by a human against the rubric

19 fields evidenced · 36 with no public information. Every value below links to the document it came from and the date we checked it.

13 of those are quoted but not yet interpreted: we hold the source sentence and the date we read it, but nobody has written the answer to the question yet. Those rows show the quote and say so rather than repeating it back as an answer. Why these exist

2 of the evidenced values quote wording our own later capture of the same page no longer contains. Marked below, awaiting an editor.

Also appears in

AI agents that support the Model Context Protocol AI agents and vendors that state HIPAA compliance

Trust gap

How this is scored

These scores are automated. A 1 or 2 counts how many fields this entry answers with a citation — not what those answers say. A 0 means every field for that dimension is recorded as undisclosed and none of the pages we captured mentions it. No one has scored this entry against the rubric yet.

Runtime governance

unscored

Are scope, spend, and authority enforced while the agent runs?

Audit trail

2/3 auto

Is there a tamper-evident record of what it actually did?

Scored from 2 evidenced field(s): audit_trail, audit_trail_immutable. Automated score; capped at 2 pending review.

Counts Audit trail and Tamper-evident log, each cited below.

Compliance

1/3 auto

Are compliance obligations attached per engagement?

Scored from 1 evidenced field(s): compliance_certs. Automated score; capped at 2 pending review.

Counts Compliance certifications, each cited below.

Outcome settlement

2/3 auto

Does payment depend on a verified result?

Scored from 2 evidenced field(s): outcome_based_pricing, settlement_mechanism. Automated score; capped at 2 pending review.

Counts Settlement mechanism and Outcome-based pricing, each cited below.

Insurance & indemnity

unscored

Can the deployment be insured, and is the customer indemnified?

Assurance

Insurance available: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Insurance carriers: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Coverage limits: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Indemnification: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Liability cap: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Audit trail: not yet interpreted
“Proof of Decision is the publicly-verifiable form of the audit receipt.”
phronesisintel.com · checked Aug 1, 2026
Tamper-evident log: not yet interpreted
“The Mnemosyne ledger is the canonical record of what was known when. Calibration accrues publicly over time; no cherry-picking.”
phronesisintel.com · checked Aug 1, 2026
Explainability: not yet interpreted
“forecast_distribution · evidence_graph · methodology_hash calibration_record — calibration class + per-class historical performance”
phronesisintel.com · checked Aug 1, 2026
Runtime governance: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Permission scopes: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Compliance certifications: HIPAA Safe Harbor
“V#3 Healthcare (HIPAA Safe Harbor)”
phronesisintel.com · checked Aug 1, 2026
Regulatory alignment: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Outcome-based pricing: the fee scales with forecast accuracy via escrow + scored settlement
“Outcome-Conditional Contingent engagement: the fee scales with forecast accuracy via escrow + scored settlement”
phronesisintel.com · checked Aug 1, 2026
Settlement mechanism: the fee scales with forecast accuracy via escrow + scored settlement
“Outcome-Conditional Contingent engagement: the fee scales with forecast accuracy via escrow + scored settlement”
phronesisintel.com · checked Aug 1, 2026
Dispute process: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
SLA terms: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Evaluation coverage: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this

Agency

Autonomy level: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Human oversight: what executes automatically vs what requires human ratification
“action_boundary — what executes automatically vs what requires human ratification”
phronesisintel.com · checked Aug 1, 2026
Goal complexity: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Action space: not yet interpreted
“The agent calls it before it commits”
phronesisintel.com · checked Aug 1, 2026
Operating environment: not yet interpreted
“Power-to-Compute Decision Monitor”
phronesisintel.com · checked Aug 1, 2026
Initiative: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this

Safety

Safety evaluations: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Red teaming: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Safety policy: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Usage restrictions: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Model or system card: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Incident reporting: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Third-party evaluations: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Data handling: not yet interpreted
“The Mnemosyne ledger is the canonical record of what was known when. Calibration accrues publicly over time; no cherry-picking.”
phronesisintel.com · checked Aug 1, 2026

Practicality

Pricing model: the fee scales with forecast accuracy via escrow + scored settlement
“Outcome-Conditional Contingent engagement: the fee scales with forecast accuracy via escrow + scored settlement”
phronesisintel.com · checked Aug 1, 2026
Price point: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Availability: not yet interpreted
“In production”
phronesisintel.com · checked Aug 1, 2026
Deployment options: not yet interpreted
“MCP + REST co-equal at every endpoint”
Not in our latest capture. This quote was on the page when we filed it. We captured the same page again on Sep 17, 2026 and it was not there. The value above has not been re-checked by an editor yet. How we re-check citations
phronesisintel.com · checked Aug 1, 2026
Integrations: not yet interpreted
“MCP + REST”
phronesisintel.com · checked Aug 1, 2026
Supported regions: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Support model: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this

Foundation models

Base models: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Model provider: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Model swappable: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Open weights: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Fine-tuning: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Context window: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this

Ecosystem

Protocols supported: MCP + REST
“MCP + REST co-equal at every endpoint”
Not in our latest capture. This quote was on the page when we filed it. We captured the same page again on Sep 17, 2026 and it was not there. The value above has not been re-checked by an editor yet. How we re-check citations
phronesisintel.com · checked Aug 1, 2026
Tool use: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Multi-agent: not yet interpreted
“Coordination & Negotiation Multi-agent auction, bid, match, route”
phronesisintel.com · checked Aug 1, 2026
API access: not yet interpreted
“View API spec”
phronesisintel.com · checked Aug 1, 2026
Open source: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Marketplace presence: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this

Impact

User base: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
Deployment scale: not yet interpreted
“In production”
phronesisintel.com · checked Aug 1, 2026
Target sectors: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this
High-risk domains: not yet interpreted
“healthcare; climate; regulatory; supply chains; space; robotics; AI/AGI; physics & materials; longevity; quantum”
phronesisintel.com · checked Aug 1, 2026
Documented incidents: no public information
phronesisintel.com · checked Aug 1, 2026 · source did not state this

Compared with

Side-by-side on the fields where Phronesis and the other entry are both on record and actually differ.