Skip to content
GSA MCP HACKATHON · THE SERVER IS THE PRODUCT

One MCP Server.
Connected Tools.
Governed Care.

Veteran Access Bridge is a governed Model Context Protocol server that connects an SI agent to patient context, appointment options, knowledge and CRM—while deterministic services enforce scope, consent and synthetic booking rules. Avery is our voice-call demonstration client.

Synthetic demonstration · No real VA appointments are booked
MCP TOOL SERVER ⌘✓▤◇
⌘ Veteran Access MCPPython FastMCP · 29 registered tools
✧ Avery is one clientVoice agent · 21 attached tools
One governed server. Verifiable tools. Protected actions.
29Registered MCP tools
21Published client attachments
8Behavior guidelines (client)
01 / MCP-powered call flow

Six stages. One governed toolchain.

Avery demonstrates the server through a Veteran voice call. Behind each step, MCP tools expose structured capabilities and trusted services enforce the decision boundaries.

01 / GREET
☎
Connect

Avery welcomes the Veteran and identifies the scheduling need.

02 / VERIFY
◈
Verify

The trusted host checks the synthetic caller's identity and call scope.

03 / RETRIEVE
▤
Retrieve

Scoped MCP tools return permitted patient and scheduling context.

04 / ROUTE
⇄
Route

Show eligible options or identify a review requirement.

05 / CONFIRM
✓
Confirm

Current consent and booking policy are validated before a write.

06 / WRAP UP
✉
Wrap up

Communicate the verified result and record supported follow-up.

02 / The MCP server at the center

MCP-exposed capabilities.
Backend-enforced authority.

The MCP server is the technical deliverable. It publishes typed tools for patient context, scheduling, knowledge and CRM. Avery is one client. Trusted host and backend services independently enforce the boundaries of every protected action.

♙
Discoverable FastMCP contracts29 registered tools, with 21 intentionally attached to the published Avery agent.
⌘
Interoperable capability groupsPatient context, scheduling, grounded knowledge and CRM follow-up.
⬡
Policy before persistenceIdentity, session scope, consent, slot and booking rules.
⌘
Veteran Access Bridge MCP ServerPython FastMCP · 29 registered tools · Scope-checked capabilities
↕ Structured MCP calls / results
✧
Avery · Published voice clientClaude Sonnet 4.6 · 8 guidelines · 21 attached tools
↕ Policy-gated service calls
⬡
Trusted host + deterministic servicesVerification · Consent · Idempotency · Audit · Receipts
VA sandbox readsSupabase synthetic recordsScoped knowledge
03 / Evidence, not just a concept

Measured. Traceable. Synthetic.

Evaluation results stay tied to their exact date and execution scope. We do not turn historical tests into claims about production scheduling.

One completed synthetic voice booking

In a documented November 16 call, Avery selected scoped tools and the trusted backend independently verified a persisted appointment and CRM evidence.

“BOOKED_SIMULATED” represents a synthetic receipt, not a real VA appointment.
✓ Receipt verified✓ CRM evidence

Security and gold-answer verification

135/135Local control checks (Nov 19)
16/16Gold answers matched (Nov 19)

Phoenix grouped saved checks; the underlying control suites used deterministic local assertions. Other adverse scenarios and hosted concurrency remain bounded or open.

Explore the evaluation evidence →

The MCP server is the bridge between useful tools and trusted decisions.

Independent hackathon technical demonstration. Synthetic records only. No production VA scheduling access.

See how the MCP works →