Codequiry

com.codequiryPublished by codequiry.comOfficial publisherv1.1.1Updated Oct 25, 2026

Source code plagiarism, peer similarity, and AI-generated-code detection for AI agents.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Codequiry is a remote MCP server that lets an AI assistant run source code plagiarism, peer similarity and AI-generated-code detection checks.

What you can do
Run source code plagiarism checks on submitted code against external sources and peer submissions, as described for AI agents. Assess similarity between peer submissions. Detect AI-generated code. The manifest lists no individual tools, so exact operations and inputs are not documented here.
When to use it
Useful when an assistant needs to evaluate code submissions for originality, compare student or team submissions for similarity, or flag likely AI-generated code as part of a review workflow.
Requirements
A remote MCP endpoint at codequiry.com over streamable HTTP. OAuth authentication is required. No environment variables or headers are declared. A Codequiry account is implied by the OAuth requirement.
Before you install
Submitted source code is sent to a third-party service for analysis, so consider confidentiality and licensing before uploading proprietary code. OAuth grants the server access under your account. No tool list is published, so review what actions it can take before connecting.

Installation

In SourceWeft

  1. Open Codequiry 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.codequiry%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": {
    "codequiry": {
      "type": "http",
      "url": "https://codequiry.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.1.1LatestSep 16, 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.