Creo factor exposure API MCP Server

by itscreo Your server? Claim it

answering

Creo factor exposure API is answering right now. Last checked 5 min ago. It exposes 4 tools.

Factor exposures and risk contribution for a portfolio, computed on the prices you send.

Uptime history 9 hours of history

9 hours agonow

100.0%

Uptime 24h

31 of 31 checks

Tools

read from the server

275 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Creo factor exposure API every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add creo --transport http https://itscreo.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://itscreo.com/mcp

~/.codex/config.toml

[mcp_servers.creo]
url = "https://itscreo.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "creo": {
      "url": "https://itscreo.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "creo": {
      "type": "http",
      "url": "https://itscreo.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

score

score_demo_portfolio

Score the five labeled SYNTH.* demo tickers. Synthetic series, not market data. Works without a key. Costs 1 credit.

score_portfolio

Compute named factor exposures and risk contribution for positions. You must supply daily close history (volume for liquidity, market_cap for size, benchmark for beta). Creo never fetches prices. Missing exposures stay null with a reason. Needs a key unless every position is a SYNTH.* ticker without history. Costs 1 credit when it succeeds; errors are free.

factors

list_factors

List factor ids, the daily closes each needs, the demo tickers and the methodology version. Free.

mint

mint_api_key

Create a free API key (100 scoring calls a day, 5 positions). Free; limited to 5 keys per IP per day. The key is shown once. Put it in your MCP client config as the x-api-key header, or pass it as the api_key argument of the scoring tools for the rest of this session.

Endpoints

URL	Transport	State	Latency	Checked
https://itscreo.com/mcp	streamable-http	answering	249 ms	5 min ago

Alternatives to Creo factor exposure API

same job, measured the same way

Valor Services & Contact

by valor-mineral-management

Explore Valor services and prepare a contact request for the user to review and send on Valor.

6 tools answering

Variantrade

by chidi09

Read your VarianTrade portfolio, positions, risk and signals. Trades are proposal-only.

answering

Returnolio

by returnolio

Read-only stock research: company scores, the Monthly Top 10, the screener and your own portfolio.

answering

Gateway Agent Tip Jar

by gatewayinformationgroup

Optional creator-support terms and private contribution receipt tools for Gateway.

3 tools answering

MCP Pear

by marvelnwachukwu

MCP server for Pear Protocol: markets, positions, orders, portfolio, and gated trade execution.

63 installs/wk local only

Open Food Facts

by domdomegg

Search and contribute to the Open Food Facts database.

374 installs/wk local only

Thryx Portfolio

by lordbasilaiassistant-sudo

Read-only MCP server for the THRYX onchain portfolio (14 contracts on Base mainnet).

40 installs/wk local only

Construction Takeoff Estimating

by esti-maite

Construction takeoff and estimating for AI agents. Measure a drawing PDF, export a priced estimate.

answering

Creo factor exposure API — questions

Answers built from our own checks of this server.

What can Creo factor exposure API do?

It exposes 4 tools, read directly from the server on our last check. Among them: list_factors, mint_api_key, score_demo_portfolio, score_portfolio. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Creo factor exposure API working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 31 of 31 checks got a reply (100.0%), average response time 275 ms. The bar chart above shows every period we have measured.

How do I connect Creo factor exposure API?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Creo factor exposure API need an API key?

No. Creo factor exposure API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Creo factor exposure API?

It answers our handshake in 275 ms on average, which is faster than 50% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.