_ registry / mcp streamable-http · checked 22h ago

creo-factor-exposure

https://itscreo.com

Registry code: 1f9358c77436251a

api record

Creo scores portfolios for named factor exposures. Call score_demo_portfolio for a first result, or score_portfolio with your own daily closes. list_factors shows how much history each factor needs. Only successful scoring costs a credit. Customers bring prices; Creo does not publish vendor market data.

endpoint
https://itscreo.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is creo-factor-exposure live?
Yes — it answered the hub's last check (checked 22h ago). It answered 100% of checks over the last 30 days.
Is creo-factor-exposure free to use?
Yes — the hub reached it with no key and no payment.
What tools does creo-factor-exposure have?
4 tools: mint_api_key, score_demo_portfolio, score_portfolio, list_factors.
Is creo-factor-exposure safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
912ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_factors open 22h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • mint_api_key unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "email": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 9 lines
  • score_demo_portfolio unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "api_key": {
          "type": "string",
          "description": "Optional. Your creo_ key, for clients that can't set the x-api-key header after connecting (for example right after mint_api_key). Prefer the header."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • score_portfolio unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "positions"
      ],
      "properties": {
        "cash": {
          "type": [
            "string",
            "number"
          ],
          "description": "Cash in USD, part of NAV."
        },
        "api_key": {
          "type": "string",
          "description": "Optional. Your creo_ key, for clients that can't set the x-api-key header after connecting (for example right after mint_api_key). Prefer the header."
        },
        "factors": {
          "type": "array",
          "items": {
            "enum": [
              "equity.market_beta.ewma.252",
              "equity.size.log_mcap",
              "equity.momentum.total_return.12_1",
              "equity.low_volatility.ewma.63",
              "equity.liquidity.amihud.63",
              "crypto.market_beta.ewma.180",
              "crypto.momentum.total_return.180_30",
              "crypto.low_volatility.ewma.30",
              "crypto.liquidity.amihud.30",
              "equity.value.book_to_price.sec",
              "equity.investment.asset_growth.sec",
              "equity.quality.gross_profitability.sec",
              "equity.quality.return_on_assets.sec"
            ],
            "type": "string"
          },
          "description": "Default: all factors for the asset classes present."
        },
        "universe": {
          "enum": [
            "client_supplied",
            "demo_synthetic"
          ],
          "type": "string"
        },
        "valid_at": {
          "type": "string",
          "format": "date-time",
          "description": "UTC cutoff ending in Z; later bars are ignored."
        },
        "benchmark": {
          "type": "object",
          "required": [
            "history"
          ],
          "properties": {
            "ticker": {
              "type": "string"
            },
            "history": {
              "type": "array",
              "items": {
                "type": "object",
                "required": [
                  "date",
                  "close"
                ],
                "properties": {
                  "date": {
                    "type": "string",
                    "format": "date",
                    "description": "YYYY-MM-DD"
                  },
                  "close": {
                    "type": [
                      "string",
                      "number"
                    ],
                    "description": "Close price in USD."
                  },
                  "volume": {
                    "type": [
                      "string",
                      "number"
                    ],
                    "description": "Units traded; needed for liquidity."
                  }
                },
                "additionalProperties": false
              },
              "minItems": 2
            }
          },
          "description": "Market series for beta, e.g. SPY closes. Without it beta is null with MISSING_BENCHMARK.",
          "additionalProperties": false
        },
        "positions": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "ticker",
              "quantity"
            ],
            "properties": {
              "close": {
                "type": [
                  "string",
                  "number"
                ],
                "description": "Valuation close in USD."
              },
              "ticker": {
                "type": "string"
              },
              "history": {
                "type": "array",
                "items": {
                  "type": "object",
                  "required": [
                    "date",
                    "close"
                  ],
                  "properties": {
                    "date": {
                      "type": "string",
                      "format": "date",
                      "description": "YYYY-MM-DD"
                    },
                    "close": {
                      "type": [
                        "string",
                        "number"
                      ],
                      "description": "Close price in USD."
                    },
                    "volume": {
                      "type": [
                        "string",
                        "number"
                      ],
                      "description": "Units traded; needed for liquidity."
                    }
                  },
                  "additionalProperties": false
                }
              },
              "quantity": {
                "type": [
                  "string",
                  "number"
                ],
                "description": "Signed units, non-zero."
              },
              "market_cap": {
                "type": [
                  "string",
                  "number"
                ],
                "description": "USD; needed for size."
              },
              "asset_class": {
                "enum": [
                  "equity",
                  "crypto"
                ],
                "type": "string"
              }
            },
            "additionalProperties": false
          },
          "minItems": 1,
          "description": "quantity > 0 is long, < 0 is short."
        }
      },
      "additionalProperties": false
    }
    arguments 178 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 1f9358c77436251a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1f9358c77436251a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1f9358c77436251a/badge.svg)](https://brick.blue/agent/1f9358c77436251a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.