14 posts tagged with "api design"

If you work in clinical research, biotech strategy, patient advocacy, or healthcare investing, the hard part is not knowing that ClinicalTrials.gov exists. The hard part is turning trial records into an answer you can use.

You may be trying to understand which sponsors are active in a disease area, whether a competitor has moved from phase 2 into phase 3, how strict the eligibility criteria are for a class of studies, or whether there are recruiting trials a patient advocacy team should know about. The raw registry has the data. Your actual job is to read across it quickly and explain what it means.

The Clinical Trials MCP server gives your AI agent a structured way to search studies, pull trial details, and summarize the result in the same conversation where the research question started.

If you work in governance research, compensation consulting, investing, board advisory, or business journalism, executive compensation data is only useful when you can compare it quickly and explain the components clearly.

The pay data lives in SEC proxy filings. Recent filings include inline XBRL tags, but the human-readable compensation tables still vary across companies. Older filings are even messier. The important numbers are inside long DEF 14A documents, footnotes, named executive officer tables, director compensation tables, pay-vs-performance sections, and company-specific formatting.

The SEC Executive Compensation MCP server is built so an agent can answer pay questions from structured SEC compensation data instead of making a user dig through proxy filings by hand.

If you work in fintech risk, bank partnerships, treasury operations, vendor diligence, or financial research, FDIC data usually appears at the moment someone needs confidence about an institution.

Is this bank FDIC-insured? What is its certificate number? Is it active? How large is it? What do its profitability metrics look like? Can I compare it to another institution without leaving the report I am writing?

The FDIC Bank Lookup MCP server gives AI agents and REST clients structured access to FDIC-insured institution data.

Every freight broker, shipper, and logistics team needs to answer the same question:

Can we trust this carrier?

The data exists. FMCSA publishes carrier data, safety records, crash counts, inspection history, out-of-service rates, authority status, and related signals. But the workflow is still clunky. People bounce between SAFER, FMCSA tools, carrier-vetting products, spreadsheets, and internal notes.

The FMCSA Carrier Safety MCP server turns that into a tool an AI agent or backend system can call directly.

H-1B wage data matters because it sits at the intersection of compensation, immigration, recruiting, and employer research.

Job seekers want to know which companies sponsor visas and what they pay. Immigration attorneys and HR teams need wage context for LCA work. Compensation teams want market benchmarks. Recruiters and analysts want employer-level sponsorship patterns.

The H-1B Visa Data MCP server turns public LCA disclosure filings into a searchable workflow for AI agents and REST clients.

If you are responsible for imports, landed-cost estimates, product classification, or customs review, HTS lookup is not an academic exercise. A wrong code changes margin, delivery timing, and compliance risk.

The first question is usually simple: "What HTS code should we use for this product?" Then the real questions start. Is the description close enough? Is there a more specific subheading? What is the general duty rate? Does a Section 301 surcharge apply? Is the result reliable enough to quote from, or does it need broker review?

The HTS Tariff MCP server is built for that first-pass classification workflow. Your agent can search tariff entries, inspect the hierarchy, pull duty fields, notice surcharge references, and turn the result into a short explanation your team can actually use.

If you work in grantmaking, nonprofit diligence, donor research, journalism, or civic analysis, IRS 990 filings are where the financial story lives. They show revenue, expenses, assets, liabilities, officer compensation, program service activity, and organizational structure.

They are also painful to work with directly.

The data is split across form variants, annual extract files, hundreds of columns, and identity joins. Organization names are not always where people expect them to be. EINs are the stable key, but users often start with a name.

The IRS 990 Nonprofit Financials MCP server turns those filings into a searchable product for AI agents and REST clients.

If you are a journalist, policy analyst, advocacy lead, investor, or researcher, lobbying disclosure is useful because it answers a live question about influence.

Who is lobbying for this company? Which clients does this firm represent? What issues are they lobbying on? Has their focus changed over time? Which trade association keeps appearing around the same bill or agency?

The Federal Lobbying Filings MCP server gives AI agents and REST clients a structured way to search and inspect lobbying records.

If you work in grantmaking, donor operations, nonprofit research, or compliance, nonprofit lookup usually starts with one practical problem: you need to know exactly which organization you are looking at.

Is this organization actually tax-exempt? What is its EIN? Is this the same charity as the one in my CRM, or a different organization with a similar name? Can I connect this record to its IRS 990 filings and see the financial picture?

The IRS Tax-Exempt Organization Lookup MCP server turns that into a tool AI agents can call directly. Search by organization name, lookup by EIN, and return structured nonprofit identity data without sending the user into a separate IRS search flow.

If you run vendor onboarding, finance operations, marketplace trust, logistics compliance, or diligence research, sanctions screening is often one step inside a bigger decision. The team is not asking for a database. They are asking whether a counterparty can move forward.

The question sounds simple: "Is this company or person on a sanctions list?" Then reality gets in the way. Which list? Which alias? Is this a close match or just a similar name? Do we need to record the source list, the country, the identifier, and the reason for the match? Is this a vendor review, a customer onboarding step, or a shipping workflow where denied-party screening is only one part of the decision?

That is what the Global Sanctions & Watchlists MCP server is built for. It gives an agent a normalized sanctions search surface so the lookup can happen inside the workflow that needs the answer.