Connect the curated research harness.

Connect once. Keep the research state.

1. Add EquityLayer as the research layer.

   claude mcp add --transport http equitylayer https://equitylayer.io/mcp

   Copy the command

   Codex, Hermes, and other MCP clients: point them at https://equitylayer.io/mcp (HTTP transport).

2. Give your agent the setup prompt.

   Set up EquityLayer as the research layer for this workspace.
   
   Use this remote MCP server:
   - Name: equitylayer
   - URL: https://equitylayer.io/mcp
   - Transport: HTTP
   
   If you can add MCP servers, add this server now. Ask for approval if this client requires it.
   If you cannot add MCP servers, show the exact command or configuration for this client. Then wait for me.
   
   After the MCP connection works, create a local research view and show the first useful update.
   
   1. Inspect the financial MCP servers, data sources, and skills that are available in this workspace.
   2. Do not add a source or access private data without my permission.
   3. Never send private or portfolio data to EquityLayer.
   4. Start with my company, theme, or investment view. Ask one question if the scope is unclear.
   5. Use EquityLayer for research context, source rules, and saved research state.
   6. Use an available connector only when it matches the required evidence and its terms allow the use.
   7. Prefer approved official sources. Record the source, date, and reporting period.
   8. Separate reported facts, management claims, inference, and missing evidence.
   9. Compare new evidence with the previous investment view.
   10. Show what changed, why it matters, affected companies, counterevidence, and the next check.
   11. Save the research view and its next trigger in this workspace. Use the returned update tool for later checks.
   
   Do not ask for email, account, broker, wallet, or execution access.
   If the MCP is unavailable, say so and do not fabricate results.

   Copy the onboarding prompt
3. Verify the connection, then start research.

   Call get_service_status to check access and language rules. A copied URL does not confirm a successful connection.

   Your agent uses approved sources and the financial connectors already in its workspace. It returns source-linked changes, affected companies, and the next check.

Machine-readable index: /llms.txt. Everything below is the reference contract behind those three tools.

Models change. Research contracts should persist.

A useful capability has a bounded job, explicit inputs, structured outputs, source provenance, a data-as-of timestamp, known limitations, and a maintainer. MCP may be the interface, but the managed research service is the product.

Every entry in the source index is published against this contract, and every research note shows how sources become dated, testable claims.

Suggested output envelope

{
  "question": "What changed since the prior quarter?",
  "data_as_of": "ISO-8601 timestamp",
  "facts": [{ "claim": "...", "source": "..." }],
  "inferences": [{ "claim": "...", "confidence": 0.72 }],
  "assumptions": ["..."],
  "risks": ["..."],
  "invalidation_conditions": ["..."],
  "capability_version": "semis-earnings@0.3.1"
}

Trust should be inspectable.

The first version should avoid one composite “accuracy” score. Show separate signals for source coverage, point-in-time integrity, schema reliability, latency, cost, maintenance recency, benchmark task results, and user reuse.

• Never infer commercial rights from “open source” alone.
• Separate data-provider terms from repository license.
• Version reputation by capability release, not only creator.
• Evaluate bounded tasks before subjective full reports.