Skip to main content
Glama
112,291 tools. Last updated 2026-04-20 10:40
  • Identify the technology stack and services used by a website. Returns framework names, CMS platform, JavaScript libraries, analytics services, CDN provider, hosting provider, and security tools detected. Use for competitive analysis, vendor intelligence, or understanding site architecture.
    Connector
  • List all custom data key-value pairs associated with an entity. Retrieve metadata, configuration settings, and custom attributes stored for services, resources, or domains. Supports pagination for entities with large amounts of custom data
    Connector
  • TOOL for retrieving current user's owned resources and work items across the Cortex workspace. FLEXIBLE REQUEST STRUCTURE: The request accepts an object with optional fields for each resource type: - myEntitiesRequest: Fetch entities (services, resources, domains) owned by the user - myTeamsRequest: Fetch teams the user belongs to - myScorecardsRequest: Fetch scorecards associated with user's entities - myOpenPRsRequest: Fetch user's open pull requests across all Git repositories - myRequestedReviewsRequest: Fetch PRs where user is requested as a reviewer - myWorkItemsRequest: Fetch work items (Jira, Linear, Azure DevOps) assigned to the user Set one or more fields to fetch multiple resource types in a single call. All results are combined into a single response array with mixed item types. RESPONSE STRUCTURE: Returns a single array of items where each item has an 'itemType' field indicating its type: - 'entity': Catalog entities (services, resources, domains) - 'team': Teams the user belongs to - 'scorecard': Scorecards for user's entities - 'pull_request': Open pull requests authored by the user - 'review_request': Pull requests where user is requested as reviewer - 'work_item': Work items (issues/tickets) assigned to the user EXAMPLES: 1. Fetch only services: {"myEntitiesRequest": {"entityTypes": ["service"]}} 2. Fetch teams and their entities: {"myTeamsRequest": {"includeMembers": true}, "myEntitiesRequest": {}} 3. Get all work (PRs, reviews, Jira tickets): {"myOpenPRsRequest": {}, "myRequestedReviewsRequest": {}, "myWorkItemsRequest": {}} 4. Search entities with filters: {"myEntitiesRequest": {"query": "payment", "ownershipSource": "DIRECT", "entityTypes": ["service", "resource"]}}
    Connector
  • [DISCOVERY] Returns the most used network pairs (chains) for a given protocol ranked by USD volume transferred The endpoint automatically selects hourly or daily aggregation based on the time range For ranges < 24 hours within the last 30 days, hourly data is used Otherwise, daily data is used — Returns the most used network pairs (chains) for a given protocol ranked by USD volume transferred The endpoint automatically selects hourly or daily aggregation based on the time range For ranges < 24 hours within the last 30 days, hourly data is used Otherwise, daily data is used Returns: { data: { from: string,
    Connector
  • Get an HN user profile with karma, about, and optionally their most recent submissions resolved into full items.
    Connector
  • List all available relationship types with pagination. View relationship type configurations to understand what kinds of relationships can be created between entities like services, resources, domains, and teams
    Connector

Matching MCP Servers

  • -
    security
    A
    license
    -
    quality
    Multi-tool MCP server for AI agents with 29 tools across web scraping, SEO analysis, screenshot and PDF generation, domain intelligence, content extraction, multi-chain EVM blockchain queries, and security toolkit. Free tier available with no auth required.
    Last updated
    54
    1
    MIT

Matching MCP Connectors