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

precis

https://mcp.precis.finance

Registry code: 83861250c4c69c48

api record

# Précis — Finance Intelligence (MCP connector)

You are connected to Précis, a FP&A data platform with read-only finance access for your organisation: query financial statements and metrics, inspect row-level detail, and build charts. Reporting tools come in variants — `run_statement`/`run_metric` show the user a table; `run_statement_data`/`run_metric_data` return the raw figures plus a `data_ref` for analysis or charting; `export_dataset(data_ref, format)` exports the cached snapshot to JSON or XLSX. To chart: call a `_data` tool, then `eval_chart_transform(data_refs, JS transform,…

endpoint
https://mcp.precis.finance/mcp
protocol
streamable-http ·2025-06-18
authentication
bearer
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 precis live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is precis free to use?
Yes — the hub reached it with no key and no payment.
What tools does precis have?
20 tools: get_binding, get_load_status, get_inspection_schema, list_variants, run_metric, precis_orientation, get_file_download, run_statement, ….
Is precis 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
99.5%

90 days 99.2%· all time 99.2%

latency
329ms

last good check

priced tools
0

of 20 tools

_ answered our checks, 90 days 380 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • run a profit and loss statement
  • break down a financial metric by dimension
  • inspect rows behind a figure
  • list planning scenarios
takes → gives
text → data
tools
17 reads
_ 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 20 tools
7 open 13 never probed 7 of 20 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_dimensions reads open 9h ago

    List the dimensions defined in the model — keys, labels, and kinds (leaf / derived / ragged hierarchy). Catalogue metadata only; use search_hierarchy to list a dimension's members.

    mcp-tool

    {
      "type": "object",
      "title": "list_dimensions",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • list_inspection_sources reads open 23h ago

    List the row-level sources available for inspection.

    mcp-tool

    {
      "type": "object",
      "title": "list_inspection_sources",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • list_kpis reads open 23h ago

    Browse the metric catalogue — metric keys, formats, domains, and the dimensions available per metric.

    mcp-tool

    {
      "type": "object",
      "title": "list_kpis",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • list_scenarios reads open 18h ago

    List the available planning scenarios and their status.

    mcp-tool

    {
      "type": "object",
      "title": "list_scenarios",
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • list_bindings reads open 9h ago

    List the configured data feeds (ingestion bindings) with their schedule — which datasets load, from where, how often.

    mcp-tool

    {
      "type": "object",
      "title": "list_bindings",
      "properties": {
        "target": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Target",
          "default": null
        },
        "source_id": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Source Id",
          "default": null
        }
      },
      "additionalProperties": false
    }
    arguments 31 lines
  • search_hierarchy reads open 9h ago

    Search the dimension hierarchies (cost centres, accounts, …) to find valid codes and ids before composing a query.

    mcp-tool

    {
      "type": "object",
      "title": "search_hierarchy",
      "properties": {
        "limit": {
          "anyOf": [
            {
              "type": "integer"
            },
            {
              "type": "null"
            }
          ],
          "title": "Limit",
          "default": null
        },
        "query": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Query",
          "default": null
        },
        "dimension": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Dimension",
          "default": null
        }
      },
      "additionalProperties": false
    }
    arguments 43 lines
  • list_load_history reads open 23h ago

    List data-load attempts from the ingestion audit trail — when each dataset landed, with what status. Answers "is April in yet?" / "when was this data last loaded?".

    mcp-tool

    {
      "type": "object",
      "title": "list_load_history",
      "properties": {
        "limit": {
          "type": "integer",
          "title": "Limit",
          "default": 50
        },
        "period": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Period",
          "default": null
        },
        "status": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Status",
          "default": null
        },
        "binding_id": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Binding Id",
          "default": null
        },
        "dataset_id": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Dataset Id",
          "default": null
        }
      },
      "additionalProperties": false
    }
    arguments 60 lines
  • get_binding reads unknown 21h ago

    Fetch one data feed's full configuration: source, target dataset, schedule, and extract parameters.

    mcp-tool

    {
      "type": "object",
      "title": "get_binding",
      "required": [
        "binding_id"
      ],
      "properties": {
        "binding_id": {
          "type": "string",
          "title": "Binding Id"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • get_load_status reads unknown 14h ago

    Fetch one data load's full detail by load_id — timestamps, status, rows landed, and any error message.

    mcp-tool

    {
      "type": "object",
      "title": "get_load_status",
      "required": [
        "load_id"
      ],
      "properties": {
        "load_id": {
          "type": "string",
          "title": "Load Id"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • get_inspection_schema reads unknown 18h ago

    Get the column schema for an inspection source.

    mcp-tool

    {
      "type": "object",
      "title": "get_inspection_schema",
      "required": [
        "source_key"
      ],
      "properties": {
        "source_key": {
          "type": "string",
          "title": "Source Key"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • list_variants reads unknown 18h ago

    List the what-if variants of a scenario.

    mcp-tool

    {
      "type": "object",
      "title": "list_variants",
      "required": [
        "scenario_id"
      ],
      "properties": {
        "scenario_id": {
          "type": "string",
          "title": "Scenario Id"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • run_metric reads unknown never probed

    Break one or more metrics down by a dimension — revenue by project, utilisation by employee, headcount trends, GL account drill-down. Rows are the dimension; columns are metrics × scenarios. Pass `scenarios` explicitly and give every scenario a concise, user-facing `alias` such as Actuals, Budget, Variance, or Var %. Returns a formatted table with structured data. The widget already displays this table to the user. Add useful interpretation; do not reproduce the table or restate all its rows in Markdown unless the user explicitly requests it or the widget is unavailable.

    mcp-tool

    {
      "type": "object",
      "title": "run_metric",
      "required": [
        "metrics"
      ],
      "properties": {
        "scale": {
          "anyOf": [
            {
              "type": "integer"
            },
            {
              "type": "null"
            }
          ],
          "title": "Scale",
          "default": null
        },
        "filters": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": true
            },
            {
              "type": "null"
            }
          ],
          "title": "Filters",
          "default": null
        },
        "metrics": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "title": "Metrics"
        },
        "decimals": {
          "anyOf": [
            {
              "type": "integer"
            },
            {
              "type": "null"
            }
          ],
          "title": "Decimals",
          "default": null
        },
        "scenarios": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "object",
                "additionalProperties": true
              }
            },
            {
              "type": "null"
            }
          ],
          "title": "Scenarios",
          "default": null
        },
        "dimensions": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            {
              "type": "null"
            }
          ],
          "title": "Dimensions",
          "default": null
        },
        "period_end": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Period End",
          "default": null
        },
        "period_start": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Period Start",
          "default": null
        }
      },
      "additionalProperties": false
    }
    arguments 109 lines
  • precis_orientation reads unknown never probed

    Call this first. Returns how to use Précis over this connector: the data model (scenarios, metrics, statements, dimensions), the reporting-tool variants, and how to build charts. Read it before composing queries.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_file_download unknown never probed

    Renew a download capability for an available, owned artifact.

    mcp-tool

    {
      "type": "object",
      "title": "get_file_download",
      "required": [
        "file_id"
      ],
      "properties": {
        "file_id": {
          "type": "string",
          "title": "File Id"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • run_statement reads unknown never probed

    Run a financial statement — P&L, variance report, or executive summary. Rows are statement lines (Revenue, Direct Cost, Gross Margin, …); columns are scenarios. Supports an optional dimension breakdown (e.g. by period or cost centre). For an unspecified general P&L, prefer `full_pnl` when it is listed by precis_orientation. Give every scenario a concise, user-facing `alias` such as Actuals, Budget, Variance, or Var %. Returns a formatted table with structured data. The widget already displays this table to the user. Add useful interpretation; do not reproduce the table or restate all its rows in Markdown unless the user explicitly requests it or the widget is unavailable.

    mcp-tool

    {
      "type": "object",
      "title": "run_statement",
      "properties": {
        "scale": {
          "anyOf": [
            {
              "type": "integer"
            },
            {
              "type": "null"
            }
          ],
          "title": "Scale",
          "default": null
        },
        "filters": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": true
            },
            {
              "type": "null"
            }
          ],
          "title": "Filters",
          "default": null
        },
        "decimals": {
          "anyOf": [
            {
              "type": "integer"
            },
            {
              "type": "null"
            }
          ],
          "title": "Decimals",
          "default": null
        },
        "scenarios": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "object",
                "additionalProperties": true
              }
            },
            {
              "type": "null"
            }
          ],
          "title": "Scenarios",
          "default": null
        },
        "statement": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Statement",
          "default": null
        },
        "dimensions": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            {
              "type": "null"
            }
          ],
          "title": "Dimensions",
          "default": null
        },
        "period_end": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Period End",
          "default": null
        },
        "period_start": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Period Start",
          "default": null
        }
      },
      "additionalProperties": false
    }
    arguments 111 lines
  • run_statement_data reads unknown never probed

    Run a financial statement — P&L, variance report, or executive summary. Rows are statement lines (Revenue, Direct Cost, Gross Margin, …); columns are scenarios. Supports an optional dimension breakdown (e.g. by period or cost centre). For an unspecified general P&L, prefer `full_pnl` when it is listed by precis_orientation. Give every scenario a concise, user-facing `alias` such as Actuals, Budget, Variance, or Var %. Returns the raw figures (and a `data_ref`) for your own analysis or to build a chart — pass `[data_ref]` as `data_refs` to eval_chart_transform. Does not show the user a table.

    mcp-tool

    {
      "type": "object",
      "title": "run_statement",
      "properties": {
        "scale": {
          "anyOf": [
            {
              "type": "integer"
            },
            {
              "type": "null"
            }
          ],
          "title": "Scale",
          "default": null
        },
        "filters": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": true
            },
            {
              "type": "null"
            }
          ],
          "title": "Filters",
          "default": null
        },
        "decimals": {
          "anyOf": [
            {
              "type": "integer"
            },
            {
              "type": "null"
            }
          ],
          "title": "Decimals",
          "default": null
        },
        "scenarios": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "object",
                "additionalProperties": true
              }
            },
            {
              "type": "null"
            }
          ],
          "title": "Scenarios",
          "default": null
        },
        "statement": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Statement",
          "default": null
        },
        "dimensions": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            {
              "type": "null"
            }
          ],
          "title": "Dimensions",
          "default": null
        },
        "period_end": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Period End",
          "default": null
        },
        "period_start": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Period Start",
          "default": null
        }
      },
      "additionalProperties": false
    }
    arguments 111 lines
  • run_metric_data reads unknown never probed

    Break one or more metrics down by a dimension — revenue by project, utilisation by employee, headcount trends, GL account drill-down. Rows are the dimension; columns are metrics × scenarios. Pass `scenarios` explicitly and give every scenario a concise, user-facing `alias` such as Actuals, Budget, Variance, or Var %. Returns the raw figures (and a `data_ref`) for your own analysis or to build a chart — pass `[data_ref]` as `data_refs` to eval_chart_transform. Does not show the user a table.

    mcp-tool

    {
      "type": "object",
      "title": "run_metric",
      "required": [
        "metrics"
      ],
      "properties": {
        "scale": {
          "anyOf": [
            {
              "type": "integer"
            },
            {
              "type": "null"
            }
          ],
          "title": "Scale",
          "default": null
        },
        "filters": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": true
            },
            {
              "type": "null"
            }
          ],
          "title": "Filters",
          "default": null
        },
        "metrics": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "title": "Metrics"
        },
        "decimals": {
          "anyOf": [
            {
              "type": "integer"
            },
            {
              "type": "null"
            }
          ],
          "title": "Decimals",
          "default": null
        },
        "scenarios": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "object",
                "additionalProperties": true
              }
            },
            {
              "type": "null"
            }
          ],
          "title": "Scenarios",
          "default": null
        },
        "dimensions": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            {
              "type": "null"
            }
          ],
          "title": "Dimensions",
          "default": null
        },
        "period_end": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Period End",
          "default": null
        },
        "period_start": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Period Start",
          "default": null
        }
      },
      "additionalProperties": false
    }
    arguments 109 lines
  • export_dataset unknown never probed

    Export a cached data_ref to json or xlsx without rerunning the query; returns a temporary file and download link.

    mcp-tool

    {
      "type": "object",
      "title": "export_dataset",
      "required": [
        "data_ref",
        "format"
      ],
      "properties": {
        "format": {
          "type": "string",
          "title": "Format"
        },
        "data_ref": {
          "type": "string",
          "title": "Data Ref"
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • inspect_rows reads unknown 21h ago

    Inspect the row-level detail behind a figure, from an enabled inspection source. Returns a capped sample for reasoning plus a grid for the user.

    mcp-tool

    {
      "type": "object",
      "title": "inspect_rows",
      "required": [
        "source_key",
        "scenario_id"
      ],
      "properties": {
        "limit": {
          "anyOf": [
            {
              "type": "integer"
            },
            {
              "type": "null"
            }
          ],
          "title": "Limit",
          "default": null
        },
        "columns": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            {
              "type": "null"
            }
          ],
          "title": "Columns",
          "default": null
        },
        "filters": {
          "anyOf": [
            {
              "type": "object",
              "additionalProperties": true
            },
            {
              "type": "null"
            }
          ],
          "title": "Filters",
          "default": null
        },
        "period_end": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Period End",
          "default": null
        },
        "source_key": {
          "type": "string",
          "title": "Source Key"
        },
        "scenario_id": {
          "type": "string",
          "title": "Scenario Id"
        },
        "period_start": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Period Start",
          "default": null
        }
      },
      "additionalProperties": false
    }
    arguments 83 lines
  • eval_chart_transform unknown 21h ago

    Create a chart from data_refs (an array of snapshot IDs), a bounded JavaScript function, and chart_spec. Supports line, bar, area, waterfall, scatter, horizontal_bar, forecast_line, cohort_heatmap and sparkline_row. Query first and inspect rows; the transform takes one result per ref and returns flat rows.

    mcp-tool

    {
      "type": "object",
      "title": "eval_chart_transform",
      "required": [
        "data_refs",
        "transform_code",
        "chart_spec"
      ],
      "properties": {
        "data_refs": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "title": "Data Refs"
        },
        "chart_spec": {
          "type": "object",
          "title": "Chart Spec",
          "additionalProperties": true
        },
        "transform_code": {
          "type": "string",
          "title": "Transform Code"
        }
      },
      "additionalProperties": false
    }
    arguments 28 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 83861250c4c69c48.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/83861250c4c69c48/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/83861250c4c69c48/badge.svg)](https://brick.blue/agent/83861250c4c69c48?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
100%

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.