Doctrine corpus index — invinoveritas MCP Resource
Doctrine corpus index
is one of 101 resources on the
invinoveritas
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Doctrine corpus index from your client
- Claude Code invinoveritas Resource/Doctrine corpus index run in your project directory
- Claude Desktop invinoveritas Resource/Doctrine corpus index ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor invinoveritas Resource/Doctrine corpus index ~/.cursor/mcp.json
- VS Code invinoveritas Resource/Doctrine corpus index .vscode/mcp.json
- Zed invinoveritas Resource/Doctrine corpus index ~/.config/zed/settings.json
- Windsurf invinoveritas Resource/Doctrine corpus index ~/.codeium/windsurf/mcp_config.json
- Cline invinoveritas Resource/Doctrine corpus index ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI invinoveritas Resource/Doctrine corpus index ~/.gemini/settings.json
- Grok invinoveritas Resource/Doctrine corpus index .mcp.json (in your project root)
- ChatGPT invinoveritas Resource/Doctrine corpus index Settings → Connectors → Advanced → Developer mode
- Claude.ai invinoveritas Resource/Doctrine corpus index Settings → Connectors → Add custom connector
- LangChain invinoveritas Resource/Doctrine corpus index pip install langchain-mcp-adapters
Other resources on this server
- Earned Rope (2026-06-04)
- Pace (2026-06-02)
- Closing the Gaps (2026-05-31)
- Fortification (2026-05-29)
- On Searching . . . and Finding (2026-05-24)
- Lessons from the Korean War (2026-05-23)
- Go Big (At Home) (2026-05-22)
- Charlemagne — The Empire Builder (2026-05-21)
- Testing (2026-05-20)
- On Bounty Hunters and Mercs (2026-05-18)
- Wildfire (2026-05-18)
- Swapping Out the Engine (2026-05-16)
- Scipio Africanus — How to Win When Everyone Expects You to Lose (2026-0…
- The Compound Interest of Discipline (2026-05-14)
- What to Do When You’re on a Nuclear Submarine and Shit Hits the Fan (20…
- Lessons from Suetonius Paulinus (2026-05-12)
- Pursuing Your Destiny (2026-05-11)
- Imagine Where You’ll Be in 3 Months (2026-05-10)
- On Tactical Patience (2026-05-08)
- From Thought to Action: The Day Agents Got Fangs (2026-05-07)
- Liberation & Empire: The Serpent and the Throne (2026-05-06)
- The Past is Not Dead. It is Not Even Past. (2026-05-05)
- 80k Is Not the Prize (2026-05-04)
- Athena and the Agents: Wisdom Before Execution (2026-05-03)
- Alignment, Adjustments & Constructive Motion (2026-04-30)
- Alignment is Macedonian, not Spartan (2026-04-28)
- Why Positioning is Everything (2026-04-28)
- When AI Starts Paying for Its Own Thoughts (2026-04-02)
- Fear Between Being and Becoming (2026-03-14)
- The Boundary (2026-03-12)
- Distributed Runtime Verification Layer (2026-03-10)
- The Rules We Can't Break (2026-03-08)
- The Age of Consolidation (2026-03-06)
- From AI Governance Theory to Protocol Design — Why Compute Escalation N…
- Determinism vs Probability — The Missing Layer in AI Governance (2026-0…
- Stress Tests: Geopolitics, Bitcoin, and Enforcement in the Real World (…
- The Age of Systems Over Humans (2026-02-27)
- Enforcement Is the Next Infrastructure Layer (2026-02-25)
- Foundations Before the Code: Aligning Governance, Risk, and Infrastruct…
- Who Verifies the Verifier? AI Code Security and Infrastructure Governan…
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.