Skip to main content
Glama
mcp-funding-investor-record

mcp-funding-investor-record

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
APIFY_TOKENYesYour Apify API token. Get it at https://console.apify.com/account/integrations

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_company_funding_recordA

Return a company's funding record from PRIMARY sources: SEC EDGAR Form D filings, UK Companies House registrations and press coverage. Returns one flat Clay ready row in which every number carries a source_of_record saying whether it came from a legal filing or a press release, because those are not the same kind of fact and merging them is the defect this tool exists to prevent. Only an EXACT entity match after corporate suffixes are stripped populates an amount; a near match such as a differently named subsidiary goes to separate related_entity columns as a named lead and can never be summed into a total. Not Crunchbase and not a resold database. Read only; requires an APIFY_TOKEN and consumes Apify credits per call.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.5/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool there is no possibility of misselection; the tool's purpose (returning a sourced company funding record) is stated unambiguously in its description.

Naming Consistency5/5

The single name get_company_funding_record follows a clear verb_noun snake_case pattern that would generalize well if more tools were added.

Tool Count3/5

One tool is thin for a server, but the scope is deliberately narrow (a single read-only lookup with a defined output schema), so a minimal surface is defensible rather than a mismatch.

Completeness4/5

For a read-only funding lookup the single operation covers the stated lifecycle end-to-end, including source attribution and exact-match rules; no create/update is expected since the domain is external public records.

Maintenance

ActivityMaintained
ResponsivenessOutdated data