Server definition

Hash: sha256:d31ca3fc4c15e4bc0a37c2df97f967263534289b057c0b74e29f27802c5837f0
What it is: What a remote MCP server returned when asked what it offers: 4 tools

The blob, as servednamed by its sha256

{
  "instructions": null,
  "tools": [
    {
      "description": "Location Groups are a way of grouping GeoNamesLocation entities into a simplified hierarchy.\n\nThey start from top-level regions using the United Nations M49 standard (Region/Sub-Region/Intermediate Region).\nThe US is further broken down United States Census Bureau regions (e.g. East/West etc) and then into individual states.\nCertain other countries are also broken down into their states/provinces: AE, CA, CN, IN.",
      "inputSchema": {
        "properties": {
          "page": {
            "description": "A page number within the paginated result set.",
            "in": "query",
            "type": "integer"
          },
          "page_size": {
            "description": "Number of results to return per page.",
            "in": "query",
            "type": "integer"
          }
        },
        "required": [],
        "type": "object"
      },
      "name": "location_groups_list",
      "outputSchema": null
    },
    {
      "description": "Creates a user account with the given email, sends a verification email, and returns an API token. Unverified users are limited to 30 queries/month; verified users can make 300/month for free. Drop us an email to tell us how you found the service and if you want more queries (see website footer)",
      "inputSchema": {
        "properties": {
          "email": {
            "description": "User email address",
            "format": "email",
            "type": "string"
          }
        },
        "required": [
          "email"
        ],
        "type": "object"
      },
      "name": "register_and_get_key_create",
      "outputSchema": null
    },
    {
      "description": "Stories by Industry/Location\nSimplified endpoint that runs the same logic as the main stories endpoint, with a restricted parameter set (industry and the location the story happened in). Stories can either be\n\n -- IndustrySectorUpdate\n\n or activities in an organization's lifecycle. We track the following activities:\n\n -- CorporateFinanceActivity: M&A, investments, stock purchases\n\n -- PartnershipActivity: Partnership between 2 or more organizations. Often, companies describe their customers as their partners. This type of activity covers both genuine partnerships and customer/supplier relationships\n\n -- RoleActivity: Key change in senior personnel, e.g. replacing CEO\n\n -- LocationActivity: Opening or closing a new location (e.g. setting up in EMEA or shutting down a factory in a particular town)\n\n -- ProductActivity: New product launches\n\n -- AnalystRatingActivity: Updates from industry analysts\n\n -- EquityActionsActivity: Stock repurchases, dividends etc\n\n -- FinancialReportingActivity: Notice that an organization is going to announce its financials\n\n -- FinancialsActivity: Information about company financials, e.g. revenue or EBITDA\n\n -- IncidentActivity: Adverse incidents e.g. safety\n\n -- LegalActivity: Lawsuits or activities that could lead to lawsuits, e.g. SEC investigations\n\n -- MarketingActivity: e.g. launching a new advertising campaign\n\n -- OperationsActivity: Company operations news, e.g. we are investing in a new product, or we have just completed an security audit\n\n -- RecognitionActivity: e.g. we are delighted to announce that we won Agency of the Year\n\n -- RegulatoryActivity: Legal or regulatory activity affecting this organizationg e.g. permit for drilling, or regulatory filing\n\n\nParameters:\n- activity_location: Location group name or id (e.g. \"texas\", \"india\", \"MidWest\", \"FR\", \"us-ca\") where the story happened. Not case sensitive. Accepts multiple values. They must each match an id or name from the [location groups](#/location-groups/location-groups_list) endpoint.\n- activity_location_id: Location group identifiers (e.g., \"Southern Asia\", \"BT\", \"US-CA\") where the story happened. Case-sensitive. Accepts multiple values. They must each match an id from the [location groups](#/location-groups/location-groups_list) endpoint.\n- include_provenance: Add a `source_audit` field to each story explaining how it was surfaced (source path, Typesense match score, and the entity that carried it). Defaults to false.\n- industry: Industry name to filter by. Accepts multiple values.\n- industry_context: Optional context aspects to anchor the industry search in. Pass each aspect as a separate value. Can be a broader category name or detailed examples (e.g. \"Movie Industry\" when searching for \"Distribution\", or \"BOPP Film\" and \"BOPET Film\" when searching for \"Film\"). Applied to every value of `industry` in the same request.\n- industry_id: Industry ID (topic ID) to filter by. Accepts multiple values. They must each match a topic_id from the [industry-clusters](#/industry-clusters/industry-clusters_list) endpoint.\n- location: Deprecated alias of `activity_location`, kept for backwards compatibility. It means the location the story happened in, not where the company is based.\n- location_id: Deprecated alias of `activity_location_id`, kept for backwards compatibility. It means the location the story happened in, not where the company is based.\n- output: Output format. Defaults to \"simple\" (SimpleStory schema). Use \"full\" for the detailed response.\n- page: A page number within the paginated result set.\n- page_size: Number of results to return per page.",
      "inputSchema": {
        "properties": {
          "activity_location": {
            "description": "Location group name or id (e.g. \"texas\", \"india\", \"MidWest\", \"FR\", \"us-ca\") where the story happened. Not case sensitive. Accepts multiple values. They must each match an id or name from the [location groups](#/location-groups/location-groups_list) endpoint.",
            "in": "query",
            "items": {
              "type": "string"
            },
            "type": "array"
          },
          "activity_location_id": {
            "description": "Location group identifiers (e.g., \"Southern Asia\", \"BT\", \"US-CA\") where the story happened. Case-sensitive. Accepts multiple values. They must each match an id from the [location groups](#/location-groups/location-groups_list) endpoint.",
            "in": "query",
            "items": {
              "type": "string"
            },
            "type": "array"
          },
          "include_provenance": {
            "description": "Add a `source_audit` field to each story explaining how it was surfaced (source path, Typesense match score, and the entity that carried it). Defaults to false.",
            "in": "query",
            "type": "boolean"
          },
          "industry": {
            "description": "Industry name to filter by. Accepts multiple values.",
            "in": "query",
            "items": {
              "type": "string"
            },
            "type": "array"
          },
          "industry_context": {
            "description": "Optional context aspects to anchor the industry search in. Pass each aspect as a separate value. Can be a broader category name or detailed examples (e.g. \"Movie Industry\" when searching for \"Distribution\", or \"BOPP Film\" and \"BOPET Film\" when searching for \"Film\"). Applied to every value of `industry` in the same request.",
            "in": "query",
            "items": {
              "type": "string"
            },
            "type": "array"
          },
          "industry_id": {
            "description": "Industry ID (topic ID) to filter by. Accepts multiple values. They must each match a topic_id from the [industry-clusters](#/industry-clusters/industry-clusters_list) endpoint.",
            "in": "query",
            "items": {
              "type": "integer"
            },
            "type": "array"
          },
          "location": {
            "description": "Deprecated alias of `activity_location`, kept for backwards compatibility. It means the location the story happened in, not where the company is based.",
            "in": "query",
            "items": {
              "type": "string"
            },
            "type": "array"
          },
          "location_id": {
            "description": "Deprecated alias of `activity_location_id`, kept for backwards compatibility. It means the location the story happened in, not where the company is based.",
            "in": "query",
            "items": {
              "type": "string"
            },
            "type": "array"
          },
          "output": {
            "description": "Output format. Defaults to \"simple\" (SimpleStory schema). Use \"full\" for the detailed response.",
            "enum": [
              "full",
              "simple"
            ],
            "in": "query",
            "type": "string"
          },
          "page": {
            "description": "A page number within the paginated result set.",
            "in": "query",
            "type": "integer"
          },
          "page_size": {
            "description": "Number of results to return per page.",
            "in": "query",
            "type": "integer"
          }
        },
        "required": [],
        "type": "object"
      },
      "name": "stories_industry_location_list",
      "outputSchema": null
    },
    {
      "description": "Stories by Organization\nSimplified endpoint that runs the same logic as the main stories endpoint, with a restricted parameter set: `org_name`, optionally narrowed by where the company is based (`org_location`), what it does (`industry`), and where its stories happened (`activity_location`). Stories can either be\n\n -- IndustrySectorUpdate\n\n or activities in an organization's lifecycle. We track the following activities:\n\n -- CorporateFinanceActivity: M&A, investments, stock purchases\n\n -- PartnershipActivity: Partnership between 2 or more organizations. Often, companies describe their customers as their partners. This type of activity covers both genuine partnerships and customer/supplier relationships\n\n -- RoleActivity: Key change in senior personnel, e.g. replacing CEO\n\n -- LocationActivity: Opening or closing a new location (e.g. setting up in EMEA or shutting down a factory in a particular town)\n\n -- ProductActivity: New product launches\n\n -- AnalystRatingActivity: Updates from industry analysts\n\n -- EquityActionsActivity: Stock repurchases, dividends etc\n\n -- FinancialReportingActivity: Notice that an organization is going to announce its financials\n\n -- FinancialsActivity: Information about company financials, e.g. revenue or EBITDA\n\n -- IncidentActivity: Adverse incidents e.g. safety\n\n -- LegalActivity: Lawsuits or activities that could lead to lawsuits, e.g. SEC investigations\n\n -- MarketingActivity: e.g. launching a new advertising campaign\n\n -- OperationsActivity: Company operations news, e.g. we are investing in a new product, or we have just completed an security audit\n\n -- RecognitionActivity: e.g. we are delighted to announce that we won Agency of the Year\n\n -- RegulatoryActivity: Legal or regulatory activity affecting this organizationg e.g. permit for drilling, or regulatory filing\n\n\nParameters:\n- activity_location: Location group name or id (e.g. \"texas\", \"india\", \"MidWest\", \"FR\", \"us-ca\") where the story happened. Not case sensitive. Accepts multiple values. They must each match an id or name from the [location groups](#/location-groups/location-groups_list) endpoint.\n- activity_location_id: Location group identifiers (e.g., \"Southern Asia\", \"BT\", \"US-CA\") where the story happened. Case-sensitive. Accepts multiple values. They must each match an id from the [location groups](#/location-groups/location-groups_list) endpoint.\n- industry: Industry name the company must work in. Narrows which companies match `org_name`. Accepts multiple values.\n- industry_context: Optional context aspects to anchor the industry search in. Pass each aspect as a separate value. Can be a broader category name or detailed examples (e.g. \"Movie Industry\" when searching for \"Distribution\", or \"BOPP Film\" and \"BOPET Film\" when searching for \"Film\"). Applied to every value of `industry` in the same request.\n- industry_id: Industry ID (topic ID) the company must belong to. Narrows which companies match `org_name`. They must each match a topic_id from the [industry-clusters](#/industry-clusters/industry-clusters_list) endpoint.\n- location: Deprecated alias of `activity_location`, kept for backwards compatibility. It means the location the story happened in, not where the company is based.\n- location_id: Deprecated alias of `activity_location_id`, kept for backwards compatibility. It means the location the story happened in, not where the company is based.\n- org_location: Location group name or id where the company is *based*. Narrows which companies match `org_name`, so it may only be used together with `org_name`. Not case sensitive. Accepts multiple values. For stories that happened in a place use `activity_location` instead.\n- org_location_id: Location group identifiers (e.g., \"Southern Asia\", \"BT\", \"US-CA\") where the company is *based*. Case-sensitive. May only be used together with `org_name`.\n- org_name: Filter by organization name (partial match). (required)\n- output: Output format. Defaults to \"simple\" (SimpleStory schema). Use \"full\" for the detailed response.\n- page: A page number within the paginated result set.\n- page_size: Number of results to return per page.",
      "inputSchema": {
        "properties": {
          "activity_location": {
            "description": "Location group name or id (e.g. \"texas\", \"india\", \"MidWest\", \"FR\", \"us-ca\") where the story happened. Not case sensitive. Accepts multiple values. They must each match an id or name from the [location groups](#/location-groups/location-groups_list) endpoint.",
            "in": "query",
            "items": {
              "type": "string"
            },
            "type": "array"
          },
          "activity_location_id": {
            "description": "Location group identifiers (e.g., \"Southern Asia\", \"BT\", \"US-CA\") where the story happened. Case-sensitive. Accepts multiple values. They must each match an id from the [location groups](#/location-groups/location-groups_list) endpoint.",
            "in": "query",
            "items": {
              "type": "string"
            },
            "type": "array"
          },
          "industry": {
            "description": "Industry name the company must work in. Narrows which companies match `org_name`. Accepts multiple values.",
            "in": "query",
            "items": {
              "type": "string"
            },
            "type": "array"
          },
          "industry_context": {
            "description": "Optional context aspects to anchor the industry search in. Pass each aspect as a separate value. Can be a broader category name or detailed examples (e.g. \"Movie Industry\" when searching for \"Distribution\", or \"BOPP Film\" and \"BOPET Film\" when searching for \"Film\"). Applied to every value of `industry` in the same request.",
            "in": "query",
            "items": {
              "type": "string"
            },
            "type": "array"
          },
          "industry_id": {
            "description": "Industry ID (topic ID) the company must belong to. Narrows which companies match `org_name`. They must each match a topic_id from the [industry-clusters](#/industry-clusters/industry-clusters_list) endpoint.",
            "in": "query",
            "items": {
              "type": "integer"
            },
            "type": "array"
          },
          "location": {
            "description": "Deprecated alias of `activity_location`, kept for backwards compatibility. It means the location the story happened in, not where the company is based.",
            "in": "query",
            "items": {
              "type": "string"
            },
            "type": "array"
          },
          "location_id": {
            "description": "Deprecated alias of `activity_location_id`, kept for backwards compatibility. It means the location the story happened in, not where the company is based.",
            "in": "query",
            "items": {
              "type": "string"
            },
            "type": "array"
          },
          "org_location": {
            "description": "Location group name or id where the company is *based*. Narrows which companies match `org_name`, so it may only be used together with `org_name`. Not case sensitive. Accepts multiple values. For stories that happened in a place use `activity_location` instead.",
            "in": "query",
            "items": {
              "type": "string"
            },
            "type": "array"
          },
          "org_location_id": {
            "description": "Location group identifiers (e.g., \"Southern Asia\", \"BT\", \"US-CA\") where the company is *based*. Case-sensitive. May only be used together with `org_name`.",
            "in": "query",
            "items": {
              "type": "string"
            },
            "type": "array"
          },
          "org_name": {
            "description": "Filter by organization name (partial match).",
            "in": "query",
            "minLength": 1,
            "type": "string"
          },
          "output": {
            "description": "Output format. Defaults to \"simple\" (SimpleStory schema). Use \"full\" for the detailed response.",
            "enum": [
              "full",
              "simple"
            ],
            "in": "query",
            "type": "string"
          },
          "page": {
            "description": "A page number within the paginated result set.",
            "in": "query",
            "type": "integer"
          },
          "page_size": {
            "description": "Number of results to return per page.",
            "in": "query",
            "type": "integer"
          }
        },
        "required": [
          "org_name"
        ],
        "type": "object"
      },
      "name": "stories_organization_list",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:d31ca3fc4c15e4bc0a37c2df97f967263534289b057c0b74e29f27802c5837f0 | sha256sum