Attest

com.askattestPublished by askattest.comOfficial publisherv1.0.0Updated Nov 4, 2026

Find your Attest studies and read their survey results, boards and key findings.

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Attest MCP server that lets an assistant find your Attest studies and read their survey results, boards and key findings.

What you can do
  • Locate Attest studies in your account
  • Read survey results from those studies
  • Read boards and key findings
  • No individual tools are documented, so the exact actions are limited to what the provider lists.
When to use it
Useful when you work with Attest survey research and want an assistant to pull study results, boards or key findings into a conversation without exporting them by hand.
Requirements
A remote MCP endpoint at mcp.askattest.com over streamable HTTP, with OAuth sign-in to an Attest account required. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to your Attest account, so the assistant can read whatever studies that account can see; review the scopes granted. The description covers reading only, but no tool list is published, so confirm what the server can actually access before connecting.

Installation

In SourceWeft

  1. Open Attest in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.askattest%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "attest": {
      "type": "http",
      "url": "https://mcp.askattest.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 4, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.