How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Daloopa MCP Server

Hosted remote MCP server (Streamable HTTP) exposing nine tools over the same fundamental dataset — discover_companies, discover_company_series, discover_company_documents, get_company_fundamentals, get_document_content, search_documents, get_stock_prices, list_skills and get_skill. Every returned datapoint carries its source location. Authenticated via MCP OAuth 2.1 with dynamic client registration and PKCE, via a 24-hour bearer token minted from an API key, or via an X-API-KEY header.

This API exposes 14 operations across 14 paths, organized into 3 resource areas, and defines 10 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.

Requests are made against the base URL https://mcp.daloopa.com/server/mcp.

14 operations 14 paths 10 schemas 9 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0.0
Base URL
https://mcp.daloopa.com/server/mcp
Resource Areas
3

Paths & Operations 14

Across 14 paths, the API surfaces 14 operations — 9 GET, 5 POST. They span 3 resource areas: Auth, Consumption, Operations. Each is listed below with its method, path, parameters, and response codes.

Auth 10
POST
/register
Register Client
register_client_register_post body → 200422
GET
/authorize
Authorize
authorize_authorize_get 6 params → 200422
POST
/login
Login
login_login_post body → 200422
POST
/sso-login
Sso Login
sso_login_sso_login_post body → 200422
GET
/mcp-sso-validation
Sso Validation
sso_validation_mcp_sso_validation_get 3 params → 200422
POST
/token
Token
token_token_post body → 200422
POST
/auth/token
Api Key Token
api_key_token_auth_token_post body → 200422
GET
/.well-known/oauth-protected-resource
Protected Resource Metadata
protected_resource_metadata__well_known_oauth_protected_resource_get → 200
GET
/.well-known/oauth-authorization-server
Well Known
well_known__well_known_oauth_authorization_server_get → 200
GET
/.well-known/openai-apps-challenge
Well Known Openai Apps Challenge
well_known_openai_apps_challenge__well_known_openai_apps_challenge_get → 200
Consumption 2
GET
/consumption
Get datapoint consumption over a time range
get_consumption_consumption_get 2 params → 200422
GET
/consumption/events
List datapoint access events over a time range
list_consumption_events_consumption_events_get 4 params → 200422
Operations 2
GET
/
Root
root__get → 200
GET
/health/
Health Check
health_check_health__get → 200

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are Body_login_login_post (7 properties), Body_token_token_post (6 properties), Body_sso_login_sso_login_post (5 properties), ConsumptionResponse (4 properties). Each schema is shown below with its type and property counts.

Body_api_key_token_auth_token_post
object
1 property 1 required
Body_login_login_post
object
7 properties 6 required
Body_register_client_register_post
object
3 properties 2 required
Body_sso_login_sso_login_post
object
5 properties 4 required
Body_token_token_post
object
6 properties
ConsumptionEvent
object
4 properties 3 required
ConsumptionEventsResponse
object
2 properties 2 required
ConsumptionResponse
object
4 properties 4 required
HTTPValidationError
object
1 property
ValidationError
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

daloopa-mcp-service-openapi.json Raw ↑
Where this information came from

This is an independent, third-party profile of Daloopa MCP Server, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.