Servidor MCP
Taproot: AT Protocol MCP
com.atproto-mcp/taproot
Herramientas para desarrolladores
Búsqueda e investigación
Redes sociales
Público y accesible
MCP 2025-11-25
Qué hace este MCP
Reads and resolves public AT Protocol data, including profiles, posts, records, threads, backlinks, repositories, lexicons, moderation labels, and identity relationships.
Capacidades
Herramientas
27
herramientas
count_records
Count the total records in an account's collection (e.g. how many likes a user has given). Scans server-side so you don't page manually. AT Protocol has no cheap exact count, so for very large collections this returns exact:false with a lower-bound count and a cursor,call again with that cursor and ADD the counts to keep going.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['repo', 'collection'], 'properties': {'repo': {'type': 'string', 'description': 'A handle or DID.'}, 'cursor': {'type': 'string', 'description': 'Resume cursor from a prior capped (exact:false) count. The new count covers records AFTER it,add it to your previous total.'}, 'collection': {'type': 'string', 'description': 'Collection NSID, e.g. app.bsky.feed.like.'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
count_repos_by_collection
Count how many accounts across the network publish a given collection/lexicon,e.g. 'how many accounts have an at.glean.subscription?'. Walks a relay's com.atproto.sync.listReposByCollection with NO per-account handle resolution, so it's cheap and returns an exact total for typical collections. For very large collections it returns exact:false with a cursor,call again with that cursor and ADD the counts (like count_records). Relay-served (defaults to the public Bluesky relay; pass `relay` for another).
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['collection'], 'properties': {'relay': {'type': 'string', 'description': 'Optional relay origin to query instead of the default, e.g. https://relay.example.com.'}, 'cursor': {'type': 'string', 'description': 'Resume cursor from a previous exact:false response.'}, 'collection': {'type': 'string', 'description': 'A collection NSID, e.g. app.bsky.feed.generator.'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
describe_pds
Describe a Personal Data Server: its DID, whether registration requires an invite, the handle domains you can register there, and ToS/contact links. Works for any PDS, not just Bluesky. Input is the PDS origin (e.g. https://pds.example.com).
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['pds'], 'properties': {'pds': {'type': 'string', 'description': 'A PDS origin URL, e.g. https://pds.example.com.'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
get_account_history
An account's history from its PLC audit log: handle changes, PDS migrations, signing-key rotations, and creation time. did:plc accounts only (did:web has no PLC log). Input is a handle or DID.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['actor'], 'properties': {'actor': {'type': 'string', 'description': 'A handle or DID (did:plc).'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
get_app_link
Turn an at:// URI (or handle/DID) into shareable web links,a Bluesky/Blacksky app URL to open in a browser, plus the canonical PDS getRecord URL. Use when the user wants a clickable/pasteable link.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['uri'], 'properties': {'uri': {'type': 'string', 'description': 'An at:// URI, handle, or DID.'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
get_backlinks
Index of who/what references a target,the inbound likes, reposts, quotes, replies, and follows,as COUNTS per category, via the Constellation backlink index. Target is a record's at:// URI or an account DID. This returns aggregate counts only; each category also includes a `source` string. To list the actual records and their author DIDs for one category (e.g. WHO liked a post), call list_backlink_records with that `source`.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['target'], 'properties': {'target': {'type': 'string', 'description': 'A record at:// URI or a DID.'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
get_blob_info
Get metadata for a single blob: its canonical PDS getBlob URL plus a best-effort content-type and byte size (via a HEAD request). Returns the URL, never the bytes. Use to turn a blob ref (CID) found in a record into a downloadable link and learn what it is. Input is the owning repo (handle or DID) and the blob CID.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['repo', 'cid'], 'properties': {'cid': {'type': 'string', 'description': "The blob CID (e.g. bafkrei...), as found in a record's blob ref."}, 'repo': {'type': 'string', 'description': "A handle or DID (the blob's owning repo)."}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
get_did_document
Fetch the raw DID document for any DID or handle: all aliases (alsoKnownAs), every service entry (PDS, labeler, custom AppView), and verification methods. Broader than get_profile, and works for did:web accounts. Input is a handle or DID.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['actor'], 'properties': {'actor': {'type': 'string', 'description': 'A handle or DID.'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
get_latest_commit
The current head commit of an account's repository (com.atproto.sync.getLatestCommit): its commit CID and revision. The cheapest way to fingerprint a repo or detect whether it changed since you last looked, without downloading data. Complements get_repo_status (which has the rev but not the commit CID). Input is a handle or DID.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['repo'], 'properties': {'repo': {'type': 'string', 'description': 'A handle or DID.'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
get_pds_directory_info
A cached health card for a PDS from pds.directory: version, DID, approximate user count, reachability, last-checked time, available domains, and which relays index it. Input is the PDS hostname (e.g. pds.example.com). Best-effort/cached data.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['hostname'], 'properties': {'hostname': {'type': 'string', 'description': 'A PDS hostname, e.g. pds.example.com.'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
get_profile
Get an account's repository overview (handle, DID, PDS, and the list of collections it contains). Input is a handle or DID.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['actor'], 'properties': {'actor': {'type': 'string', 'description': 'A handle (alice.bsky.social) or DID (did:plc:...).'}, 'include': {'type': 'array', 'items': {'enum': ['schema', 'backlinks', 'profile'], 'type': 'string'}, 'description': "Optional enrichments: 'schema' resolves the collection's lexicon; 'backlinks' lists who referenced the target; 'profile' adds the repo owner's display name, bio, and avatar URL."}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
get_record
Fetch a single record by its full at:// URI (must include collection and rkey). Returns the record's value, CID, and resolved identity.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['uri'], 'properties': {'uri': {'type': 'string', 'description': 'Full at:// URI: at://<did-or-handle>/<collection>/<rkey>.'}, 'include': {'type': 'array', 'items': {'enum': ['schema', 'backlinks', 'profile'], 'type': 'string'}, 'description': "Optional enrichments: 'schema' resolves the collection's lexicon; 'backlinks' lists who referenced the target; 'profile' adds the repo owner's display name, bio, and avatar URL."}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
get_relay_directory_info
A cached overview of a relay from firehose.directory: counts of PDSes it indexes (total/active/offline/banned) and total accounts. Input is the relay hostname (e.g. bsky.network). Best-effort/cached data.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['hostname'], 'properties': {'hostname': {'type': 'string', 'description': 'A relay hostname, e.g. bsky.network.'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
get_repo_status
Liveness/moderation status of an account's repository: whether it is active, its current revision, and any takedown/suspended/deactivated/deleted state. Answers 'has @alice been taken down?' which get_profile can't. Input is a handle or DID.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['repo'], 'properties': {'repo': {'type': 'string', 'description': 'A handle or DID.'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
get_thread
Reconstruct the conversation around a post: its ancestor chain up to the thread root (following reply.parent, root-first) PLUS a bounded descendant reply TREE,replies, replies-to-replies, and so on, each tagged with its depth and parent,walked breadth-first and capped for cost. NOTE: descendant expansion assumes the Bluesky reply model (app.bsky.feed.post with reply.parent); ancestor walking follows reply.parent generically, but the reply tree is specific to that lexicon and will be empty for record types that model replies differently. Answers 'show me this whole conversation / what is this replying to?'. If the tree is truncated, use list_backlink_records on a specific post's URI to expand it further. Input is a post's at:// URI.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['uri'], 'properties': {'uri': {'type': 'string', 'description': "A post's full at:// URI: at://<did-or-handle>/app.bsky.feed.post/<rkey>."}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
list_backlink_records
List the actual records (author DID + verified handle + at:// URI, newest first) that reference a target for ONE category,i.e. WHO liked, reposted, quoted, replied to, mentioned, or follows it. Workflow: call get_backlinks first to get a category `source`, then pass it here. To read WHAT a referencing record says (e.g. the text of a mention or reply), call get_record on its at:// URI. Author handles are resolved via identity resolution (verified), not search.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['target', 'source'], 'properties': {'limit': {'type': 'integer', 'maximum': 25, 'minimum': 1, 'description': 'Page size (1-25, default 25). Use the returned cursor for the next page.'}, 'cursor': {'type': 'string', 'description': 'Pagination cursor returned by a previous call (to get the next page).'}, 'source': {'type': 'string', 'description': 'A category `source` from get_backlinks, e.g. app.bsky.feed.like:subject.uri.'}, 'target': {'type': 'string', 'description': 'The referenced record at:// URI or account DID (same target passed to get_backlinks).'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
list_blobs
List the blobs (uploaded media/attachments,images, video, etc.) hosted in an account's repository, via com.atproto.sync.listBlobs. Returns each blob's CID and its canonical PDS getBlob URL (PDS-native, works for any PDS,not a CDN). Answers 'what media does this account host?'. Records reference blobs by CID; use this (or get_blob_info) to turn a CID into a fetchable URL. Input is a handle or DID.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['repo'], 'properties': {'repo': {'type': 'string', 'description': 'A handle or DID.'}, 'limit': {'type': 'integer', 'maximum': 100, 'minimum': 1, 'description': 'Page size (1-100, default 50). A cursor in the response means more pages exist.'}, 'cursor': {'type': 'string', 'description': 'Pagination cursor from a previous call.'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
list_labelers
List the labeler (moderation) services known to the labeler relay,each labeler's DID, resolved handle, and service endpoint. The discovery step BEFORE query_labels, which needs a labeler DID/handle up front: use this to find moderation.bsky.app and any third-party/regional labelers, then pass one to query_labels.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'properties': {'limit': {'type': 'integer', 'maximum': 20, 'minimum': 1, 'description': 'Page size (1-20, default 20). Use the returned cursor for the next page.'}, 'cursor': {'type': 'string', 'description': 'Pagination cursor from a previous call.'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
list_records
List records in a collection for an account, with pagination. Provide the repo (handle or DID) and the collection NSID (e.g. app.bsky.feed.post).
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['repo', 'collection'], 'properties': {'repo': {'type': 'string', 'description': 'A handle or DID.'}, 'limit': {'type': 'integer', 'maximum': 100, 'minimum': 1, 'description': 'Page size (1-100, default 50). A cursor in the response means more pages exist.'}, 'cursor': {'type': 'string', 'description': 'Pagination cursor from a previous page.'}, 'collection': {'type': 'string', 'description': 'Collection NSID, e.g. app.bsky.feed.post.'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
list_repos
List the accounts (repositories) hosted on a PDS, via com.atproto.sync.listRepos: each repo's DID and active/takedown status, paginated. Answers 'who is hosted on this PDS?' / 'how many accounts does this PDS have?'. By default returns DIDs only (one request, large page — best for counting); pass enrich=true to also resolve handles (slower, smaller page). Input is the PDS origin (e.g. https://pds.example.com). Works for any PDS.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['pds'], 'properties': {'pds': {'type': 'string', 'description': 'A PDS origin URL, e.g. https://pds.example.com.'}, 'limit': {'type': 'integer', 'maximum': 1000, 'minimum': 1, 'description': 'Page size (1-1000, default 1000). With enrich=true the effective page is capped near 20 (each DID is resolved to a handle). Use the returned cursor for the next page.'}, 'cursor': {'type': 'string', 'description': 'Pagination cursor from a previous call.'}, 'enrich': {'type': 'boolean', 'description': 'Resolve each DID to its handle. Default false — returns DIDs only in ONE request (large page, the fast path for listing/counting). Set true only when you need handles (slower, smaller page).'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
list_repos_by_collection
Network-wide: which accounts publish a given collection/lexicon,e.g. 'who has an app.bsky.feed.generator (a custom feed)?' or who uses a custom lexicon. Via a relay's com.atproto.sync.listReposByCollection (anonymous). By default returns DIDs only (one request, large page); pass enrich=true to also resolve handles (slower, smaller page). For just a total, use count_repos_by_collection. NOTE: relay-served (defaults to the public Bluesky relay; pass `relay` to query another), not the account's own PDS. Pairs with search_lexicons / resolve_lexicon.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['collection'], 'properties': {'limit': {'type': 'integer', 'maximum': 1000, 'minimum': 1, 'description': 'Page size (1-1000, default 1000). With enrich=true the effective page is capped near 20 (each DID is resolved to a handle). Use the returned cursor for the next page.'}, 'relay': {'type': 'string', 'description': 'Optional relay origin to query instead of the default, e.g. https://relay.example.com.'}, 'cursor': {'type': 'string', 'description': 'Pagination cursor from a previous call.'}, 'enrich': {'type': 'boolean', 'description': 'Resolve each DID to its handle. Default false — returns DIDs only in ONE request (large page, the fast path for listing/counting). Set true only when you need handles (slower, smaller page).'}, 'collection': {'type': 'string', 'description': 'A collection NSID, e.g. app.bsky.feed.generator.'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
query_labels
What moderation labels a labeler has applied to a subject (com.atproto.label.queryLabels),e.g. 'has @alice or this post been labeled spam/nsfw/hidden by labeler X?'. Anonymous and service-agnostic: the labeler's own service endpoint is found from its DID document (no hardcoded aggregator). Subject is a DID/handle (account labels) or an at:// URI (record labels); labeler is the handle or DID of a labeler service (e.g. moderation.bsky.app).
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['subject', 'labeler'], 'properties': {'limit': {'type': 'integer', 'maximum': 100, 'minimum': 1, 'description': 'Page size (1-100, default 50). A cursor in the response means more pages exist.'}, 'cursor': {'type': 'string', 'description': 'Pagination cursor from a previous call.'}, 'labeler': {'type': 'string', 'description': 'The labeler service to ask,a handle or DID, e.g. moderation.bsky.app.'}, 'subject': {'type': 'string', 'description': 'What to check: a DID/handle (account-level labels) or an at:// URI (record-level).'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
resolve
Resolve any AT Protocol identifier to JSON. Accepts an at:// URI (at://<did-or-handle>/<collection>/<rkey>), a bare handle (alice.bsky.social), or a DID (did:plc:...). Returns a profile, a collection page, or a single record depending on how specific the input is. PDS-agnostic: works for any AT Protocol PDS, not just Bluesky.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['uri'], 'properties': {'uri': {'type': 'string', 'description': 'An at:// URI, a bare handle, or a DID.'}, 'limit': {'type': 'integer', 'maximum': 100, 'minimum': 1, 'description': 'Page size (1-100, default 50). A cursor in the response means more pages exist.'}, 'cursor': {'type': 'string', 'description': 'Pagination cursor (collections only).'}, 'include': {'type': 'array', 'items': {'enum': ['schema', 'backlinks', 'profile'], 'type': 'string'}, 'description': "Optional enrichments: 'schema' resolves the collection's lexicon; 'backlinks' lists who referenced the target; 'profile' adds the repo owner's display name, bio, and avatar URL."}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
resolve_lexicon
Explain what a record type means by resolving its lexicon schema. Input is a collection NSID (e.g. app.bsky.feed.post). Returns the schema's description and definition.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['nsid'], 'properties': {'nsid': {'type': 'string', 'description': 'A collection NSID, e.g. app.bsky.feed.post.'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
search_accounts
Search for AT Protocol accounts by handle or display name (paginated, via the Bluesky AppView app.bsky.actor.searchActors, so accounts unknown to that index may be missing). Returns candidate accounts with DID + handle, to turn a name into a DID. Results are search CANDIDATES, not verified handle-to-DID mappings: call verify_handle before trusting that a handle really belongs to a DID (resolve/get_profile only confirm an account exists, not that the handle is authentic).
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['query'], 'properties': {'limit': {'type': 'integer', 'maximum': 100, 'minimum': 1, 'description': 'Page size (1-100, default 50). A cursor in the response means more pages exist.'}, 'query': {'type': 'string', 'description': 'A handle fragment or display name, e.g. "alice".'}, 'cursor': {'type': 'string', 'description': 'Pagination cursor from a previous call.'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
search_lexicons
Browse or search the registry of published AT Protocol lexicon schemas. The response's `total` field is the exact registry size and `matched` is the exact match count. Substring matches the NSID or description (query 'profile' → anything containing 'profile'); prefix the query with a DOT for a suffix match (query '.profile' → only NSIDs ENDING in .profile, i.e. profile record types). Filter by schema kind with `type` — 'give me every space lexicon' is type='space' with NO query, since an NSID does not imply its type (space.saebyeok.permissionSet is a permission set; app.kimbia.circle is a space). Types: the spec's primary types are record, query, procedure, subscription, and permission-set; a main def may also be a non-primary type (object, token, string); space comes from proposal 0016 (permissioned data), which is not in the ratified spec; defs-only marks a schema file with no main definition. Every response carries a `typeCounts` breakdown of the returned matches (it sums to `matched`), so one call with no arguments shows which kinds exist and how many; when you filter by type, `otherTypes` reports what the filter excluded, so a too-narrow or misspelled type still shows you the real options. Without a query or type, returns the total plus a sample. Results are paginated by `limit`; to see matches beyond the first page, call again with the `offset` printed at the end of the list. Use resolve_lexicon for a specific schema's full definition.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'properties': {'type': {'oneOf': [{'type': 'string'}, {'type': 'array', 'items': {'type': 'string'}}], 'description': 'Keep only these schema kinds, e.g. "space" for permissioned space declarations, or ["record","procedure"]. Case-insensitive. Combine with query to search within a kind.'}, 'limit': {'type': 'integer', 'maximum': 100, 'minimum': 1, 'description': 'Page size (1-100, default 50). A cursor in the response means more pages exist.'}, 'query': {'type': 'string', 'description': 'Optional substring to filter by, e.g. "profile" or "app.bsky".'}, 'offset': {'type': 'integer', 'minimum': 0, 'description': 'Skip this many matches (pagination). Use the offset value printed after a truncated list.'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
verify_handle
Bidirectionally verify that a handle is really owned by its DID, via DNS TXT and HTTPS well-known. Returns whether each method passed. Use this to check for impersonation/spoofing,search results and resolve give candidates, this gives cryptographic binding.
Solo lectura
Acceso externo
Esquema de entrada
{'type': 'object', 'required': ['handle'], 'properties': {'handle': {'type': 'string', 'description': 'A handle, e.g. alice.bsky.social.'}}, 'additionalProperties': False}
Esquema de salida
{'type': 'object', 'additionalProperties': True}
Historial
Cambios recientes en herramientas
Añadido
get_thread
17 de September de 2026 a las 12:33
Añadido
list_labelers
17 de September de 2026 a las 12:33
Añadido
get_blob_info
17 de September de 2026 a las 12:33
Añadido
list_blobs
17 de September de 2026 a las 12:33
Añadido
count_repos_by_collection
17 de September de 2026 a las 12:33
Añadido
list_repos_by_collection
17 de September de 2026 a las 12:33
Añadido
query_labels
17 de September de 2026 a las 12:33
Añadido
get_relay_directory_info
17 de September de 2026 a las 12:33
Añadido
get_pds_directory_info
17 de September de 2026 a las 12:33
Añadido
get_app_link
17 de September de 2026 a las 12:33
Añadido
get_did_document
17 de September de 2026 a las 12:33
Añadido
verify_handle
17 de September de 2026 a las 12:33
Añadido
get_latest_commit
17 de September de 2026 a las 12:33
Añadido
get_repo_status
17 de September de 2026 a las 12:33
Añadido
list_repos
17 de September de 2026 a las 12:33
Añadido
describe_pds
17 de September de 2026 a las 12:33
Añadido
resolve_lexicon
17 de September de 2026 a las 12:33
Añadido
search_lexicons
17 de September de 2026 a las 12:33
Añadido
get_account_history
17 de September de 2026 a las 12:33
Añadido
search_accounts
17 de September de 2026 a las 12:33
Añadido
count_records
17 de September de 2026 a las 12:33
Añadido
list_backlink_records
17 de September de 2026 a las 12:33
Añadido
get_backlinks
17 de September de 2026 a las 12:33
Añadido
list_records
17 de September de 2026 a las 12:33
Añadido
get_record
17 de September de 2026 a las 12:33
Añadido
get_profile
17 de September de 2026 a las 12:33
Añadido
resolve
17 de September de 2026 a las 12:33
Descubrir
Servidores MCP similares
Social Fetch
io.github.social-freak-ltd/socialfetch
Retrieves public content and metadata from social networks, music services, Facebook Marketplace, events, profiles, posts, commen…
apis-io
io.apis/apis-io
Provides catalog search, comparison, scoring, enrichment, lists, and dataset exports for APIs, providers, specifications, workflo…
Tools for Agents
io.github.max124vip-dev/tools-for-agents
Provides web research and extraction workflows, crawling, browser automation, PDF and book OCR, text processing, embeddings, and …
API Direct
io.apidirect/api-direct
Searches and retrieves data from social networks, news and Google services, while also providing Amazon product, seller, ranking,…
canton-ccpedia
io.github.UnityNodes/canton-ccpedia
Searches and explains Canton Network and Daml documentation, governance proposals, forums, code examples, APIs, releases, and eco…
webbersites-x402-data-api
io.github.webberdesign/webbersites-x402-data-api
Provides pay-per-call utilities for web scraping, SEO and accessibility audits, document extraction, DNS and email checks, crypto…
TERM
app.term/forum
Provides an agent-oriented forum for publishing findings, discussing questions, voting, communities, and deterministic research c…
api-evangelist
com.apievangelist/api-evangelist
Provides API governance analysis, OpenAPI overlays and version diffs, security-sensitive field classification, code samples, matu…