Creo factor exposure API

com.itscreoPublished by itscreo.comOfficial publisherv0.1.0Updated Nov 8, 2026

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

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

Creo scores a portfolio for named factor exposures and risk contribution using daily closes you supply; a remote endpoint with a free demo mode.

What you can do
  • List factor ids, required history, demo tickers and methodology version
  • Score the five synthetic SYNTH.* demo tickers without a key
  • Score your own positions for named factor exposures and risk contribution from daily closes you provide
  • Create a free API key (100 scoring calls a day, 5 positions) and use it for the session
When to use it
Useful when you want factor exposure and risk-contribution numbers for a portfolio and already have daily close history to send. The demo tickers let you try the scoring flow before supplying real data or a key.
Requirements
Remote streamable HTTP endpoint; no local install. An x-api-key header is needed for real portfolios, or the api_key argument on scoring tools; without it only SYNTH.* demo tickers score. You must supply daily close history, plus volume for liquidity, market_cap for size and benchmark for beta. A free key can be minted via the mint_api_key tool.
Before you install
Scoring consumes credits (1 per successful call); the free tier is 100 calls a day and 5 positions, with 5 keys per IP per day. The minted key is shown only once, so store it safely. Your price history is sent to a third-party service, and Creo does not fetch prices itself, so results depend on the data you provide.

Installation

In SourceWeft

  1. Open Creo factor exposure API in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.itscreo%2Fcreo/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "creo-factor-exposure-api": {
      "type": "http",
      "url": "https://itscreo.com/mcp"
    }
  }
}

Tools

4

list_factors

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

Takes no parameters.

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.

Parametersemail

score_demo_portfolio

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

Parametersapi_key

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.

Parameterscashapi_keyfactorsuniversevalid_atbenchmarkpositionsrequired

Version history

1
  1. v0.1.0LatestNov 8, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.